You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Freedman (JIRA)" <de...@myfaces.apache.org> on 2010/03/18 22:58:29 UTC
[jira] Created: (PORTLETBRIDGE-131) If redirect occurs within JSF
rendering -- don't write/flush output
If redirect occurs within JSF rendering -- don't write/flush output
-------------------------------------------------------------------
Key: PORTLETBRIDGE-131
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-131
Project: MyFaces Portlet Bridge
Issue Type: Bug
Components: Impl
Affects Versions: 2.0.0-alpha, 1.0.0-beta
Reporter: Michael Freedman
Assignee: Michael Freedman
Current code checks to see if a redirect occurred from within the JSP during rendering and does the right thing -- but not after executing the JSF tree (that resulted from the dispatch). Need to check again and if the JSF code (via EL) triggered a redirect also terminate without writing/flushing buffers. This will allow the portlet 2.0 followon forward to work because the response won't have been committed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PORTLETBRIDGE-131) If redirect occurs within JSF
rendering -- don't write/flush output
Posted by "Michael Freedman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Freedman resolved PORTLETBRIDGE-131.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.0.0
> If redirect occurs within JSF rendering -- don't write/flush output
> -------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-131
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-131
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0-beta, 2.0.0-alpha
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 1.0.0, 2.0.0
>
>
> Current code checks to see if a redirect occurred from within the JSP during rendering and does the right thing -- but not after executing the JSF tree (that resulted from the dispatch). Need to check again and if the JSF code (via EL) triggered a redirect also terminate without writing/flushing buffers. This will allow the portlet 2.0 followon forward to work because the response won't have been committed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.