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 2009/04/29 23:13:30 UTC
[jira] Created: (PORTLETBRIDGE-65) Client directed views should
also invalidate redirect cache
Client directed views should also invalidate redirect cache
-----------------------------------------------------------
Key: PORTLETBRIDGE-65
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-65
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
The bridge caches a redirect target if the redirect occurs during a render until the view resulting from the redirect can get encoded into a render parameter. I.e. it uses the redirect cache vs. the encoded target in the incoming request until the next action. This cache is currently flushed and its contents ignored if a subsequent request is for a different portlet mode. The cache should also be ignored/flushed if the client directly expresses the target view (via the indicated request parameters). The code doesn't currently do the later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PORTLETBRIDGE-65) Client directed views should
also invalidate redirect cache
Posted by "Michael Freedman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Freedman resolved PORTLETBRIDGE-65.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.0.0
redirect cache is now cleared if the client specifies the target view.
> Client directed views should also invalidate redirect cache
> -----------------------------------------------------------
>
> Key: PORTLETBRIDGE-65
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-65
> 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
>
>
> The bridge caches a redirect target if the redirect occurs during a render until the view resulting from the redirect can get encoded into a render parameter. I.e. it uses the redirect cache vs. the encoded target in the incoming request until the next action. This cache is currently flushed and its contents ignored if a subsequent request is for a different portlet mode. The cache should also be ignored/flushed if the client directly expresses the target view (via the indicated request parameters). The code doesn't currently do the later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.