You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Neil Griffin (JIRA)" <ji...@apache.org> on 2018/09/07 17:48:00 UTC

[jira] [Updated] (PLUTO-732) TCK: PortletURLGenerationListener feature not tested by the TCK

     [ https://issues.apache.org/jira/browse/PLUTO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neil Griffin updated PLUTO-732:
-------------------------------
    Attachment: com.liferay.url.listener.portlet.zip

> TCK: PortletURLGenerationListener <ordinal> feature not tested by the TCK
> -------------------------------------------------------------------------
>
>                 Key: PLUTO-732
>                 URL: https://issues.apache.org/jira/browse/PLUTO-732
>             Project: Pluto
>          Issue Type: Bug
>          Components: tck
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Neil Griffin
>            Assignee: Scott Nicklous
>            Priority: Major
>         Attachments: com.liferay.url.listener.portlet.zip
>
>
> Section 13.6.3 of the Portlet 3.0 Spec indicates:
> {quote}
> The @PortletListener annotation designates a portlet URL generation listener class. The portlet URL generation listener class must implement the PortletURLGenerationListener interface.
> If more than one class is annotated, the order of execution is determined by the ordinal
> element within the @PortletListener annotation. Methods in annotated classes with a lower  ordinal number are executed before methods in classes with a higher ordinal number. If two annotated classes have the same ordinal number, the methods of both will be executed, but the
> execution order will be undetermined.
> {quote}
> In addition {{<ordinal>>}} sub-element has been added as an equivalent in portlet.xml -- For example:
> {code:xml|title=WEB-INF/portlet.xml}
> <listener>
> 	<ordinal>2</ordinal>
> 	<listener-class>com.mycompany.ListenerX</listener-class>
> </listener>
> <listener>
> 	<ordinal>0</ordinal>
> 	<listener-class>com.mycompany.ListenerY</listener-class>
> </listener>
> <listener>
> 	<ordinal>1</ordinal>
> 	<listener-class>com.mycompany.ListenerZ</listener-class>
> </listener>
> {code}
> This issue serves as a task for fortifying the TCK with tests that verify the ordering requirements listed above.
> Attached is an example portlet that has console logging messages showing the execution order of PortletURLGenerationListeners.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)