[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-68.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.0.0
Cache of these query string parameters is now properly cleared.
> Handling default/client directed viewIds with querystrings not cached/cleared
> correctly
> ---------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-68
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-68
> 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 is required to deal with encoded view targets that have query
> strings. The params in the query string are added to the params returned by
> the ExternalContext getRequestParams... api. This work however is delayed
> until the api is called so we don't prematurey cause parameters to be read
> (in the portlet api) and thus disable other behavior. Unfortunately, the
> temporary cache isn't getting cleared either when the cache is copied (on the
> first reference) or if a subsequent recomputation is done. This leads to the
> cache being added to follow on request parameters.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
