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 2008/07/09 20:37:31 UTC
[jira] Created: (PORTLETBRIDGE-40) Redirect during render doesn't
refresh properly
Redirect during render doesn't refresh properly
-----------------------------------------------
Key: PORTLETBRIDGE-40
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-40
Project: MyFaces Portlet Bridge
Issue Type: Bug
Components: Impl
Affects Versions: 1.0.0, 2.0.0
Reporter: Michael Freedman
Assignee: Michael Freedman
The redirect during render support doesn't retain the redirect URL across requests. If a user refreshes the portlet the original (before redirect) url is targeted. Though this results in the redirect replaying this doesn't always yield identical results than if you targeted the redirect url directly. This is because Faces (extensions) may encode additional state/info in the query string of the redirect url which changes each time such a redirect would be issued. To function properly the bridge must cache the redirect url, and detect that it should use it on subsequent refreshes (renders prior to action) instead of causing the redirect logic to be triggered all over again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PORTLETBRIDGE-40) Redirect during render doesn't
refresh properly
Posted by "Michael Freedman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Freedman resolved PORTLETBRIDGE-40.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.0.0
As per previous comment. I have now merged this code from the 1.0 code line to the 2.0 codeline so bug is fixed in both versions.
> Redirect during render doesn't refresh properly
> -----------------------------------------------
>
> Key: PORTLETBRIDGE-40
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-40
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0, 2.0.0
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 1.0.0, 2.0.0
>
>
> The redirect during render support doesn't retain the redirect URL across requests. If a user refreshes the portlet the original (before redirect) url is targeted. Though this results in the redirect replaying this doesn't always yield identical results than if you targeted the redirect url directly. This is because Faces (extensions) may encode additional state/info in the query string of the redirect url which changes each time such a redirect would be issued. To function properly the bridge must cache the redirect url, and detect that it should use it on subsequent refreshes (renders prior to action) instead of causing the redirect logic to be triggered all over again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PORTLETBRIDGE-40) Redirect during render doesn't
refresh properly
Posted by "Michael Freedman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616706#action_12616706 ]
Michael Freedman commented on PORTLETBRIDGE-40:
-----------------------------------------------
This has been fixed in the Portlet 1.0 Bridge codeline but hasn't yet been fixed in the 2.0 codeline hence the bug is left open as a reminder to merge the work.
> Redirect during render doesn't refresh properly
> -----------------------------------------------
>
> Key: PORTLETBRIDGE-40
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-40
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0, 2.0.0
> Reporter: Michael Freedman
> Assignee: Michael Freedman
>
> The redirect during render support doesn't retain the redirect URL across requests. If a user refreshes the portlet the original (before redirect) url is targeted. Though this results in the redirect replaying this doesn't always yield identical results than if you targeted the redirect url directly. This is because Faces (extensions) may encode additional state/info in the query string of the redirect url which changes each time such a redirect would be issued. To function properly the bridge must cache the redirect url, and detect that it should use it on subsequent refreshes (renders prior to action) instead of causing the redirect logic to be triggered all over again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.