Neil Griffin created PLUTO-785:
----------------------------------
Summary: Some portlets are not registered with the portlet
container when a portlet.xml descriptor contains multiple <portlet> entries
Key: PLUTO-785
URL: https://issues.apache.org/jira/browse/PLUTO-785
Project: Pluto
Issue Type: Bug
Components: portlet container
Affects Versions: 3.1.0
Reporter: Neil Griffin
Assignee: Neil Griffin
Fix For: 3.1.1
h2. Problem Background
There is a bug in Apache Pluto 3.1.x that prevents portlets from being
registered with the portlet container when a portlet.xml descriptor contains
multiple {{<portlet>}} entries. This is not a problem on Liferay Portal / DXP
or Pluto 2.0.3.
h2. Steps to Reproduce
- Checkout ([the 5.x branch of
liferay-faces-bridge.impl.git|https://github.com/liferay/liferay-faces-bridge-impl/tree/5.x])
- Build the jsf-ipc-pub-render-params-portlet with the {{-P pluto}} profile
- Copy the resulting WAR to Apache Pluto 3.x
- Visit the following URL: http://localhost:9080/pluto/portal/jsf-prp
(/) Expected Results
Both the {{jsf-ipc-pub-render-params-customers}} and
{{jsf-ipc-pub-render-params-bookings}} portlets are rendered
(x) Actual Results
The {{jsf-ipc-pub-render-params-bookings}} portlet is rendered twice
Note that when adding the Customers portlet to a page by itself, it still
renders as the {{jsf-ipc-pub-render-params-bookings}} portlet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
