[
https://issues.apache.org/jira/browse/TRINIDAD-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017552#comment-13017552
]
Prakash Udupa commented on TRINIDAD-2073:
-----------------------------------------
This caused a regression. The essence of the issue that this fix caused is
that, row selections are tried to be remembered via. a
org.apache.myfaces.trinidad.change.RowKeySetAttributeChange object added to the
ChangeManager. After ChangeManager restores, the requisite initialization in
the model has not happened, so this caused scores of exceptions. This change
needs to be backed out for now and we need to figure out to solve the side
effects first. I suggest reversing these changes, and keep this issue open.
> Session based changes fail to apply for facelets VDL
> ----------------------------------------------------
>
> Key: TRINIDAD-2073
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2073
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Facelets
> Affects Versions: 2.0.0-beta-2
> Reporter: Prakash Udupa
> Attachments: TRINIDAD-2073.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> SessionChangeManager stored changes are not applied for Facelets pages. These
> work well for JSPs, where we invoke the change application methods in
> SessionChangeManager from the document tag handler. For facelets we need to
> call these methods similarly in a suitable point in the lifecycle, either in
> the document handler or soon after the view is built.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
