[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-228.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
2.0.1
Updated portlet.xml to switch order of the tags to give correct XML syntax
> supported-publishing-event and supported-processing-event ordering is
> incorrect according to portlet-app_2_0.xsd
> ----------------------------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-228
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-228
> Project: MyFaces Portlet Bridge
> Issue Type: TCK Challenge
> Components: TCK
> Affects Versions: 2.0.0
> Environment: N/A
> Reporter: Neil Griffin
> Assignee: Michael Freedman
> Fix For: 2.0.1, 3.0.0
>
>
> [Test Challenger Name and Company]
> Neil Griffin, Liferay, Inc.
> [Specification Name(s) and Version(s)]
> Portlet 2.0 Bridge for JavaServer™ Faces 1.2
> [Test Suite Name and Version]
> portlet-bridge-tck-main, v1.0.0
> [Exclude List Version]
> N/A
> [Test Name]
> All portlets that invoke Events based IPC.
> [Complaint (argument for why test is invalid)]
> The portlet-bridge-tck-main/src/main/webapp/portlet.xml descriptor has the
> following specified multiple times:
> {code}
> <supported-publishing-event>
> <qname
> xmlns:bridge="http://myfaces.apache.org/portlet-bridge/event_ns";>bridge:myfaces.apache.org.tck.testEvent</qname>
> </supported-publishing-event>
> <supported-processing-event>
> <qname
> xmlns:bridge="http://myfaces.apache.org/portlet-bridge/event_ns";>bridge:myfaces.apache.org.tck.testEvent</qname>
> </supported-processing-event>
> {code}
> But this is invalid according to the portlet-app_2_0.xsd XML Schema, and it
> is causing Liferay Portal to refuse to deploy the portlet.
> The fix is to swap the order of each occurrence, so that
> supported-processing-event appears before supported-publishing-event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
