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

Leonardo Uribe resolved MYFACES-3588.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0

This feature is complete. We have provided a default (url) mode and another one 
(client) from MyFaces CODI. For now there is no additional work to do.
                
> window-id support
> -----------------
>
>                 Key: MYFACES-3588
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3588
>             Project: MyFaces Core
>          Issue Type: New Feature
>          Components: JSR-344
>    Affects Versions: 2.0.14, 2.1.8
>            Reporter: Gerhard Petracek
>            Assignee: Leonardo Uribe
>             Fix For: 2.2.0
>
>         Attachments: MYFACES-3588-1.patch
>
>
> as discussed at http://s.apache.org/gpT we should try to implement 
> ClientWindow (specified for jsf v2.2) also for myfaces-core 2.0.x and 2.1.x 
> as a proprietary feature. we need a myfaces specific api in 
> org.apache.myfaces.* (not in javax.faces) which matches 1:1 with the upcoming 
> api for jsf 2.2 and can be used by myfaces-core itself (to fix the 
> state-saving and scope issues in case of multi-tab constellations) as well as 
> by myfaces specific adapters (which will be provided e.g. by myfaces codi and 
> deltaspike).
> if possible/useful myfaces-core 2.2.x should use the same implementation and 
> the new api in javax.faces should just delegate to the myfaces specific api.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to