[ https://issues.apache.org/jira/browse/MYFACES-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462618 ]
Ryan Wynn commented on MYFACES-1518: ------------------------------------ As a reference this is what I am trying to do -> http://www-128.ibm.com/developerworks/websphere/library/techarticles/0608_engehausen/0608_engehausen.html JSR 168 redirects to absolute URLs are fine. So why does it become a feature for MyFaces JSR 168 portlets. Is there no other way of propogating the viewId from the action phase to the render phase? Don't get me wrong I agree using a render parameter is the cleanest way, but in this case it's limiting. > Redirect in portlet does not work because of Render Parameter > ------------------------------------------------------------- > > Key: MYFACES-1518 > URL: https://issues.apache.org/jira/browse/MYFACES-1518 > Project: MyFaces Core > Issue Type: New Feature > Components: Portlet_Support > Environment: Windows, Linux > Reporter: Ryan Wynn > > At the end of the portlet action phase the MyFacesGenericPortlet sets a > render parameter. > response.setRenderParameter(VIEW_ID, facesContext.getViewRoot().getViewId()); > This is not allowed if redirect has already been called on the external > context during the action phase of the jsf lifecycle. I believe for redirect > case a flag should be used to indicate the the render parameter should not be > set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira