Neil Griffin created PLUTO-732:
----------------------------------
Summary: 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.1, 3.0.0
Reporter: Neil Griffin
Assignee: Scott Nicklous
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)
