Troubleshooting - Last day of work in 2018




The above error in console means that the classes in com.liferay.portal.search.web.internal.display.context are not accessible. The probable cause of this issue is either the mismatch version of dependencies, or unexported package from Liferay Api.

If the version of dependencies defined in build.gradle matches the version bundled in liferay 7.1(can be figured out through App Manager under Configuration), the next step is to look into export-package list in bnd.bnd in Liferay Api







Only the packages listed in 'Export-Package' can be accessible, and there is no other way around to access to unexported package outside. (That is how OSGI works)
If you do really want to access this portal-search-web, you can remove this default module from OSGI and re-build a new portal-search-web with your customization which requires lots of work.

In the case of overriding JSP, there is no need to do the aforementioned way. It can be done by the JSP overrides using OSGI fragment way.


https://dev.liferay.com/de/develop/tutorials/-/knowledge_base/7-1/jsp-overrides-using-osgi-fragments


https://community.liferay.com/blogs/-/blogs/osgi-fragment-bundles

Comments

Post a Comment

Popular posts from this blog

Portlet Edit Mode (Portlet preference) to replace Portlet configuration

Within the  EDIT  portlet mode, a portlet should provide content and logic that lets a user customize the behavior of the portlet Typically, portlets in  EDIT  portlet mode will set or update portlet preferences. Add the following properties to the MVCPortlet component annotation. "javax.portlet.portlet-mode=text/html;edit" "javax.portlet.init-param.edit-template=/edit.jsp" And then If you go into the grid button on the portlet, 'Preference' option will appear which redirects you to edit.jsp
Read more

GoGo Shell & What can be deleted in Liferay Instance

In Liferay Instance, remove 'state' in osgi & 'work' in tomcat to remove all histories. GoGoShell is for checking the current state of each jar files in modules. pen cmd as admin and type 'telnet localhost 11311' lb : list all the jar files with state stop 70 (jar file numner) / start 70 (uninstall 70 but for deletion, it would be better to delete jar file from module folder physically) )
Read more