[
https://issues.apache.org/jira/browse/OFBIZ-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143088#comment-16143088 ]
Jacques Le Roux commented on OFBIZ-9653:
----------------------------------------
Yes that's weird. Normally request-redirect redirect also parameters, unlike request-redirect-noparam:
{code}
<xs:enumeration value="request-redirect">
<xs:annotation>
<xs:documentation>
Send a redirect down to the browser telling it to go to the new request.
Automatically redirect all current request parameters to the new request or only redirected parameters if specified.
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="request-redirect-noparam">
<xs:annotation>
<xs:documentation>
Send a redirect down to the browser telling it to go to the new request.
No current request parameters are sent to the new request, nor redirected parameters if specified.
</xs:documentation>
</xs:annotation>
</xs:enumeration>
{code}
Since you suggest (did not test but I guess it's OK)
- <response name="success" type="request-redirect" value="viewprofile"/>
+ <response name="success" type="request-redirect" value="viewprofile">
+ <redirect-parameter name="partyId"/>
+ </response>
{code}
It must be that request-redirect behaviour has changed :(
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)