You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Ryan Wynn (JIRA)" <de...@myfaces.apache.org> on 2007/01/05 21:53:27 UTC
[jira] Created: (MYFACES-1518) Redirect in portlet does not work
because of Render Parameter
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: Bug
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
[jira] Commented: (MYFACES-1518) Redirect in portlet does not work
because of Render Parameter
Posted by "Stan Silvert (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462630 ]
Stan Silvert commented on MYFACES-1518:
---------------------------------------
Yes, redirects to absolute URLs should be OK. My bad, I thought you were talking about using <redirect/> in JSF navigation.
If you do a redirect to an absolute URL then you should call FacesContext.responseComplete(). Then setRenderParameter() will not be called.
> 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
[jira] Commented: (MYFACES-1518) Redirect in portlet does not work
because of Render Parameter
Posted by "Yury Kats (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462613 ]
Yury Kats commented on MYFACES-1518:
------------------------------------
"in portlets" as in "between JSPs within the same portlet", I assume? There's nothing unsupprted about redirecting someplace else, is there?
> 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: Bug
> 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
[jira] Commented: (MYFACES-1518) Redirect in portlet does not work
because of Render Parameter
Posted by "Ryan Wynn (JIRA)" <de...@myfaces.apache.org>.
[ 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
[jira] Commented: (MYFACES-1518) Redirect in portlet does not work
because of Render Parameter
Posted by "Stan Silvert (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462610 ]
Stan Silvert commented on MYFACES-1518:
---------------------------------------
In general, redirects are not supported in JSF portlets. This is a topic being discussed as part of the JSR-301 (JSF Portlet Bridge) expert group. While it may be possible, nobody is really sure how to do it at this point.
> 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: Bug
> 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