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/07/25 19:01:46 UTC

[jira] Created: (TRINIDAD-124) Remove WrapperCompatibleExternalContext from Trinidad GlobalConfiguratorImpl for 301

Remove WrapperCompatibleExternalContext from Trinidad GlobalConfiguratorImpl for 301
------------------------------------------------------------------------------------

                 Key: TRINIDAD-124
                 URL: https://issues.apache.org/jira/browse/TRINIDAD-124
             Project: MyFaces Trinidad
          Issue Type: Bug
    Affects Versions: 1.2.1-core
         Environment: JSR-301, Portlet, JSF 1.2
            Reporter: Scott O'Bryan
             Fix For: 1.2.2-core


Initially, supporting custom PortletRequest and PortletResponse objects using JSF's ExternalContext setRequest and setResponse was not in scope due to the lack of request and response wrappers in JSR-168.  The latest released of the JSR-301 specification support these custom objects and so this code for the "WrapperCompatibleExternalContext" must be removed in order to handle dispatches correctly.

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


[jira] Updated: (TRINIDAD-124) Remove WrapperCompatibleExternalContext from Trinidad GlobalConfiguratorImpl for 301

Posted by "Scott O'Bryan (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/TRINIDAD-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Status: Patch Available  (was: Open)

> Remove WrapperCompatibleExternalContext from Trinidad GlobalConfiguratorImpl for 301
> ------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-124
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-124
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions: 1.2.1-core
>         Environment: JSR-301, Portlet, JSF 1.2
>            Reporter: Scott O'Bryan
>             Fix For: 1.2.2-core
>
>         Attachments: trinidad-124.patch
>
>
> Initially, supporting custom PortletRequest and PortletResponse objects using JSF's ExternalContext setRequest and setResponse was not in scope due to the lack of request and response wrappers in JSR-168.  The latest released of the JSR-301 specification support these custom objects and so this code for the "WrapperCompatibleExternalContext" must be removed in order to handle dispatches correctly.

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


[jira] Updated: (TRINIDAD-124) Remove WrapperCompatibleExternalContext from Trinidad GlobalConfiguratorImpl for 301

Posted by "Adam Winer (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/TRINIDAD-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Winer updated TRINIDAD-124:
--------------------------------

    Resolution: Fixed
      Assignee: Adam Winer
        Status: Resolved  (was: Patch Available)

Fixed in 1.2.2.

> Remove WrapperCompatibleExternalContext from Trinidad GlobalConfiguratorImpl for 301
> ------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-124
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-124
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Portlet
>    Affects Versions: 1.2.1-core
>         Environment: JSR-301, Portlet, JSF 1.2
>            Reporter: Scott O'Bryan
>            Assignee: Adam Winer
>             Fix For: 1.2.2-core
>
>         Attachments: trinidad-124.patch
>
>
> Initially, supporting custom PortletRequest and PortletResponse objects using JSF's ExternalContext setRequest and setResponse was not in scope due to the lack of request and response wrappers in JSR-168.  The latest released of the JSR-301 specification support these custom objects and so this code for the "WrapperCompatibleExternalContext" must be removed in order to handle dispatches correctly.

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