[
https://issues.apache.org/jira/browse/MYFACES-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972650#action_12972650
]
Leonardo Uribe commented on MYFACES-3002:
-----------------------------------------
I checked it and the test Jakob provide works correctly. I commit a variant to
check the case with redirect:
return "viewparam.xhtml?faces-redirect=true&includeViewParams=true";
It works, I don't see any problem. The idea is simple: just let the algorithm
be executed on build view time form tags inside f:metadata, and handle f:event
because it is an special case. Note Jakob provided a JUnit test for this one,
so if there is something wrong, that test should fail and prevent myfaces from
compile. It could be good if you can check if you are using the latest myfaces
version from trunk.
> 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.
