Portlet Descriptor to OSGi Service Property Map

Here’s a map of portlet XML descriptor values to OSGi service properties for publishing OSGi Portlets. The properties centralize and simplify portlet configuration. They are typically represented as key-value pairs or, more generally, as a Map-like object.

The property keys essentially flatten the XML descriptors but resemble the descriptor names.

The mappings are organized by descriptor type:

• Standard portlet descriptor. Property keys use this prefix: javax.portlet.

• Liferay descriptor descriptor. Property keys use this prefix: com.liferay.portlet. The Liferay descriptors are grouped further by descriptor file name:

  • liferay-display.xml
  • liferay-portlet.xml

The standard portlet descriptor mappings are first.

Portlet Descriptor Mappings

Note: XPath notation derived from the Portlet XSD 4 is used for simplicity.

Liferay Descriptor Mappings

Liferay Display

Liferay Portlet

Note: XPath notation derived from Liferay Portlet 5 is used for simplicity.

• [1] Portlets are registered as concrete objects.

• [2] Multiples of these properties may be used. This results in an array of values.

• [3] This type is registered as an OSGi service.

• [4] https://xmlns.jcp.org/xml/ns/portlet/portlet-app_3_0.xsd

• [5] liferay-portlet-app_[version].dtd

• [6] Here’s an example of using multiple javax.portlet.dependency properties.

  Old:

  <portlet>
  	...
  	<dependency>
  		<name>jquery</name>
  		<scope>com.jquery</scope>
  		<version>2.1.1</version>
  	</dependency>
  	<dependency>
  		<name>jsutil</name>
  		<scope>com.mycompany</scope>
  		<version>1.0.0</version>
  	</dependency>
  	...
  </portlet>
  

  New:

  @Component(
      ...
      property = {
          ...
          "javax.portlet.dependency=jquery;com.jquery;2.1.1",
          "javax.portlet.dependency=jsutil;com.mycompany;1.0.0",
          ...
      }, service = Portlet.class
  )
  public class MyPortlet extends GenericPortlet {
      ...
  }
  

• [7] Here’s an example for the com.liferay.portlet.header-request-attribute-prefix property.

  Old:

  <portlet>
  	...
  	<header-request-attribute-prefix>com.mycompany</header-request-attribute-prefix>
  	...
  </portlet>
  

  New:

  @Component(
      property = {
          ...
          "javax.portlet.dependency=jsutil;com.mycompany;1.0.0",
          "com.liferay.portlet.header-request-attribute-prefix=com.mycompany",
          ...
      }, service = Portlet.class
  )
  public class MyPortlet extends GenericPortlet {
      ...
  }
  

• [8] Here’s an example for the javax.portlet.listener property.

  Old:

  <portlet>
      ...
      <listener>
          <listener-class>com.mycompany.MyPortletURLGenerationListener</listener-class>
          <ordinal>1</ordinal>
      </listener>
      ...
  </portlet>
  

  New:

  @Component(
      property = {
          ...
          "javax.portlet.listener=com.mycompany.MyPortletURLGenerationListener;1",
          ...
      }, service = Portlet.class
  )
  public class MyPortlet extends GenericPortlet {
      ...
  }
  

• [9] An javax.portlet.init-param property can be declared like this:

  @Component(
      ...
      property = {
          ...
          "javax.portlet.init-param.myInitParam=1234",
          ...
      }, service = PortletFilter.class
  )
  public class MyFilter implements RenderFilter {
      ...
  }
  

• [10] Liferay creates each portlet’s ID based on the portlet’s name (i.e., the portlet-name descriptor in liferay-portlet.xml or the javax.portlet.name OSGi service property). Dashes, periods, and spaces are allowed in the portlet name, but they and all other JavaScript unsafe characters are stripped from the name value that’s used for the portlet ID. Therefore, make your portlet name unique in light of the characters that are removed. Otherwise, if you try to deploy a portlet whose ID is the same as a portlet that’s already deployed, your portlet deployment fails and Liferay logs this message:

  Portlet id [portletId] is already in use