Yeah, this patch was reversed because we had some issues. It works
under a bear-bones environment but when some other state-managers are
introduced, this patch blows up. I'll reassign it to 1.2.5 since it
primarily only impacts the portal environment which is still
experimental anyway.
Scott
Matthias Weßendorf (JIRA) wrote:
[ https://issues.apache.org/jira/browse/TRINIDAD-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545186 ]
Matthias Weßendorf commented on TRINIDAD-798:
---------------------------------------------
scotty,
I see some related commits, but issue is still open
StateManagerImpl extends StateManager rather then StateManagerWrapper
---------------------------------------------------------------------
Key: TRINIDAD-798
URL: https://issues.apache.org/jira/browse/TRINIDAD-798
Project: MyFaces Trinidad
Issue Type: Bug
Components: Portlet
Affects Versions: 1.2.3-core
Environment: JSR-168
Reporter: Scott O'Bryan
Assignee: Scott O'Bryan
Fix For: 1.2.4-core
Attachments: trinidad-798.patch
In JSF 1.1, there was no StageManagerWrapper provided by JSF so we were
extending the base StateManager. In 1.2 this class was provided in order to
support the delegation chain. This delegation chain is important to support
the JSR-301's portlet bridge.
Trinidad's StateManagerImpl should be changed to extend JSF1.2's
StateManagerWrapper class in order to support this delegation chain. The
mechanism used in 1.1 is not sufficient for 1.2 extensions which may require a
StateManager.
