Details
-
Bug
-
Status: Verified
-
Resolution: Unresolved
-
7.2.X, 7.3.X, Master
-
None
-
- 7.2-could
- 7.3-known-issues
- 7.3-should
- 7.4-known-issues
- liferay-ga1-ce-740
- liferay-ga1-dxp-7413
- liferay-ga10-ce-743
- liferay-ga11-ce-743
- liferay-ga12-ce-743
- liferay-ga13-ce-743-known-issue
- liferay-ga14-ce-743-known-issues
- liferay-ga15-ce-743-known-issues
- liferay-ga16-ce-743-known-issues
- liferay-ga17-ce-743-known-issues
- liferay-ga18-ce-743-known-issues
- liferay-ga19-ce-743-known-issues
- liferay-ga2-ce-741
- liferay-ga20-ce-743-known-issues
- liferay-ga21-ce-743-known-issues
- liferay-ga22-ce-743-known-issues
- liferay-ga23-ce-743-known-issues
- liferay-ga24-ce-743-known-issues
- liferay-ga25-ce-743-known-issues
- liferay-ga26-ce-743-known-issues
- liferay-ga27-ce-743-known-issues
- liferay-ga28-ce-743-known-issues
- liferay-ga29-ce-743-known-issues
- liferay-ga30-ce-743-known-issues
- liferay-ga31-ce-743-known-issues
- liferay-ga32-ce-743-known-issues
- liferay-ga33-ce-743-known-issues
- liferay-ga34-ce-743-known-issues
- liferay-ga35-ce-743-known-issues
- liferay-ga36-ce-743-known-issues
- liferay-ga37-ce-743-known-issues
- liferay-ga38-ce-743-known-issues
- liferay-ga39-ce-743-known-issues
- liferay-ga4-ce-733
- liferay-ga4-ce-743
- liferay-ga40-ce-743-known-issues
- liferay-ga41-ce-743-known-issues
- liferay-ga42-ce-743-known-issues
- liferay-ga44-ce-743-known-issues
- liferay-ga45-ce-743-known-issues
- liferay-ga46-ce-743-known-issues
- liferay-ga47-ce-743-known-issues
- liferay-ga48-ce-743-known-issues
- liferay-ga49-ce-743-known-issues
- liferay-ga5-ce-734
- liferay-ga5-ce-743
- liferay-ga50-ce-743-known-issues
- liferay-ga51-ce-743-known-issues
- liferay-ga52-ce-743-known-issues
- liferay-ga53-ce-743-known-issues
- liferay-ga54-ce-743-known-issues
- liferay-ga55-ce-743-known-issues
- liferay-ga56-ce-743-known-issues
- liferay-ga57-ce-743-known-issues
- liferay-ga58-ce-743-known-issues
- liferay-ga59-ce-743-known-issues
- liferay-ga6-ce-735
- liferay-ga6-ce-743
- liferay-ga60-ce-743-known-issues
- liferay-ga61-ce-743-known-issues
- liferay-ga62-ce-743-known-issues
- liferay-ga63-ce-743-known-issues
- liferay-ga64-ce-743-known-issues
- liferay-ga65-ce-743-known-issues
- liferay-ga66-ce-743-known-issues
- liferay-ga67-ce-743-known-issues
- liferay-ga68-ce-743-known-issues
- liferay-ga69-ce-743-known-issues
- liferay-ga7-ce-736
- liferay-ga7-ce-743
- liferay-ga8-ce-737
- liferay-ga8-ce-743
- liferay-ga9-ce-743
- liferay-u1-dxp-7413
- liferay-u2-dxp-7413
-
4
Description
Problem Background:
When there is a name clash with a private render parameter on a javax.portlet.ActionURL (submitted via <form action="${actionURL}">) and an action parameter (submitted via an <input> form field), the action parameter is not accessible via ActionRequest.getActionParameters().
Requirements for this scenario are not covered in the Portlet 3.0 Specification document. In addition, requirements are not found in the Javadoc for javax.portlet.BaseURL. Finally, the use-case is not covered by the Portlet 3.0 TCK.
Steps to Reproduce:
- Deploy the attached portlet onto Liferay
- Add "V3 Parameter Test Portlet" to a page
- Enable "Single Value"
- Input Parameter Name: p1
- Input Parameter Value: v1
- Send
- Assert render parameters display in "Currently set render parameters"
- Enable "Single Value"
- Enable checkbox "remove parameter"
- Input Parameter Name: p1
- Input Parameter Value: v1
- Send
Expected Result:
Parameter p1,v1 is removed.
Actual Result:
No parameters are removed.
The processAction method is running "getActionParameters()", but this is only returning the text values, not the remType or setType (these are null). The portlet will assume default values when they are not defined.
This portlet is working as expected when deployed on Apache Pluto.
Form is defined here: https://github.com/apache/portals-pluto/blob/e40641687ef7b88a950f9d36fa58ad447cc62d9e/demo/v3-demo-portlet/src/main/webapp/WEB-INF/jsp/view-ptp.jsp#L57
Portlet method is here: https://github.com/apache/portals-pluto/blob/e40641687ef7b88a950f9d36fa58ad447cc62d9e/demo/v3-demo-portlet/src/main/java/org/apache/portals/pluto/demo/v3/ParamTestPortlet.java#L127
Portlet can be manually built by:
- git clone https://github.com/apache/portals-pluto
- cd portals-pluto/demo/v3-demo-portlet
- mvn -P all,liferay clean install
- cp target/*.war LIFERAY_HOME/deploy