[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-86.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.0.0
> Extra parameters on a viewId can cause view target miss on subsequent request
> and hence a restore view fail
> -----------------------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-86
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-86
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 1.0.0, 2.0.0
>
>
> The bridge allows viewIds to contain query strings (for the default view and
> for switching between modes/etc. in faces-config.xml navigation rules).
> Faces impls don't deal with these extra params well. The bridge works around
> issue by temporarily removing the params and then adding them back --
> [between delegation to Faces in getActionURL and createView] -- this leads
> faces to think a view id is X while its in fact X?params. This can cause
> misses on restoreView.
> To fix this migrate the extra params to a request attribute and have the
> bridge handle concating together when it need to -- otherwise both bridge and
> Faces think/see viewId as QueryStringless.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
