As noted in response to message posted on stackoverflow, adding the escapeXml attribute valued to false provides a workaround.

<portlet:actionURL var="addUserURL" escapeXml="false">
	<portlet:param name="javax.portlet.action" value="addUser" />
</portlet:actionURL>

Action URL generated by GateIn 3.3 PC looks like :

  • when no escapeXml attribute is present :
    http://localhost:8080/portal/classic/home/demo-gtn?
    portal:componentId=8d1b7990-55c6-461a-acc7-616d055f36a1&
    interactionstate=JBPNS_rO0ABXcsABRqYXZheC5wb3J0bGV0LmFjdGlvbgAAAAEAB2FkZFVzZXIAB19fRU9GX18*&
    portal:type=action&
    portal:isSecure=false
  • when escapeXMl="false" is present :
    http://localhost:8080/portal/classic/home/demo-gtn?
    navigationalstate=JBPNS_rO0ABXcjAAZhY3Rpb24AAAABAAx2aWV3VXNlckZvcm0AB19fRU9GX18*&
    portal:componentId=8d1b7990-55c6-461a-acc7-616d055f36a1&
    interactionstate=JBPNS_rO0ABXcsABRqYXZheC5wb3J0bGV0LmFjdGlvbgAAAAEAB2FkZFVzZXIAB19fRU9GX18*&
    portal:type=action&
    portal:isSecure=false

I notice that an additional parameter navigationalstate is added when the escapeXML attribute is valued to false.

This parameter wasn't required in previous GateIn versions, maybe something wrong on this side.
Indeed, an ActionURL sent to a GenericPortlet doesn't require this attribute even if we are in GateIn 3.3.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira