You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Scott O'Bryan (JIRA)" <de...@myfaces.apache.org> on 2007/11/08 22:03:50 UTC

[jira] Updated: (TRINIDAD-798) StateManagerImpl extends StateManager rather then StateManagerWrapper

     [ https://issues.apache.org/jira/browse/TRINIDAD-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott O'Bryan updated TRINIDAD-798:
-----------------------------------

    Status: Patch Available  (was: 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
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.