[PLUTO-704] PortletV3Demo RedirectPortlet has incomplete/non-validating definition in portlet.xml

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.1
• Component/s: demo portlets
• Assignee: Neil Griffin (Inactive)
• Reporter: Neil Griffin (Inactive)
• Created: 20/Apr/18 18:45
• Updated: 14/Dec/22 14:37
• Resolved: 20/Apr/18 18:47

Description

It is possible to register a portlet both with @PortletConfiguration and in portlet.xml, but the registration definition in portlet.xml will take precedence. For example, the PortletV3Demo has a portlet definition registered via annotation:

RedirectPortlet.java

@PortletConfiguration(portletName="V3RedirectPortlet")
public class RedirectPortlet extends GenericPortlet {
    ...
}

But it is also registered in the the portlet.xml descriptor:

portlet.xml

   <portlet>
      <portlet-name>V3RedirectPortlet</portlet-name>
      <portlet-info>
         <title>Redirect Test Portlet</title>
      </portlet-info>
   </portlet>

The problem is that the XML definition is incomplete/non-validating since it does not contain a <supports>...</supports> element.

Since the demo portlet does not seem to be testing whether or not portlet.xml takes precedence, the proposed solution would be to remove incomplete/non-validating definition from portlet.xml and specify the portlet title in the annotation:

RedirectPortlet.java

@PortletConfiguration(
      portletName="V3RedirectPortlet",
      title = @LocaleString(value = "Redirect Test Portlet"))
public class RedirectPortlet extends GenericPortlet {
    ...
}