[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan resolved PORTLETBRIDGE-17.
----------------------------------------
Resolution: Fixed
Committed to trunk. Thanks Mike for catching and reporting this issue.
> Bridge faces-config.xml doesn't configure the bridge's StateManager
> -------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-17
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-17
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0-SNAPSHOT
> Reporter: Michael Freedman
> Assignee: Scott O'Bryan
> Fix For: 1.0.0-SNAPSHOT
>
> Attachments: statemgrcgf.patch
>
>
> We recently supplied a patch that included a fix that had the bridge update
> the VIEW_STATE id it cached across action/renders to account for navigations
> after the action. This involved having the bridge provide a StateManager
> impl so it could parse out the value for this id being written into the
> rendition. Unfortunately the patch neglected to carry the corresponding
> change to the bridges faces-config.xml and hence the "feature" was never
> enabled.
> To test for this -- perform an action whose result is to navigate to a
> different view (for rendering). After the first rendition suceeds -- do a
> browser refresh. Without the configuration the resulting rendering will be
> of the action view page not the rendition view page.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
