As you create portlets and customizations, it’s helpful to look up details fast. These articles provide “cheat sheets” (references) for back-end development:

  • Listing of classes moved to different JARs and/or packages.
  • Mapping of old descriptors to new equivalents (e.g., OSGi properties)
  • Listing of third-party packages Portal Core provides.

Enjoy the convenient back-end development details at your fingertips!

Liferay Portal Startup Phases

Knowing Liferay’s startup phases helps you troubleshoot startup failures. By learning the phase triggered events, you can listen for phases and act on them. This article describes the startup...

Read More

Third Party Packages Portal Exports

The com.liferay.portal.bootstrap module exports many third party Java packages that can cause problems if used improperly. If your WAR’s Gradle file, for example, uses the compile scope for a...

Read More

Portlet Descriptor to OSGi Service Property Map

This article maps portlet XML descriptor values to OSGi service properties for publishing OSGi Portlets. OSGi service definitions can use properties. OSGi service properties centralize and simplify...

Read More

Classes Moved from portal-service.jar

To leverage the benefits of modularization in Liferay Portal CE 7.1, many classes from former Liferay Portal 6 JAR file portal-service.jar have been moved into application and framework API...

Read More

OSGi Service Access

Accessing an OSGi service depends on the type of code (e.g., Spring Bean, OSGi component, etc.) accessing it and the code’s application context. Accessing Code Service Access Method Service Builder...

Read More
0 (0 Votes)
Embedding Widgets in Page Fragments Previous