[
https://issues.apache.org/jira/browse/MYFACES-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972581#action_12972581
]
Mark Struberg commented on MYFACES-3002:
----------------------------------------
It most probably is, because our internally released version is from 29. august
2010 and 2.0.2 already crashed for me (and had a few other bugs which got
fixed in the meantime too).
I debugged into it and the problem is really that
FaceletCompositionContextImpl#finalizeForDeletion() drops the
javax_faces_metadata from the ViewRoots _facetMap. After that the viewParam
information from the restoreView phase is gone...
> FaceletComponsitionContextImpl drops viewParams
> -----------------------------------------------
>
> Key: MYFACES-3002
> URL: https://issues.apache.org/jira/browse/MYFACES-3002
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.2, 2.0.3
> Reporter: Mark Struberg
> Assignee: Jakob Korherr
> Priority: Critical
>
> This is related to MYFACES-2774
> FaceletComponsitionContextImpl#finalizeForDeletion drops the
> 'javax_faces_metadata' from the UIViewRoot s _facetMap. Thus all 'old'
> viewParams are not available for propagation to the next view anymore.
> This situation happens if an action returns something like
> > return "nextPage.xhtml??faces-redirect=true&includeViewParams=true";
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
