You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2009/12/05 00:29:20 UTC

[jira] Resolved: (ORCHESTRA-45) Support for JSF 2.0

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

Leonardo Uribe resolved ORCHESTRA-45.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4
         Assignee: Leonardo Uribe

Module for jsf 2.0 created and added some tests.

> Support for JSF 2.0
> -------------------
>
>                 Key: ORCHESTRA-45
>                 URL: https://issues.apache.org/jira/browse/ORCHESTRA-45
>             Project: MyFaces Orchestra
>          Issue Type: Improvement
>          Components: FrameworkAdapter
>    Affects Versions: 1.3.1
>            Reporter: Martin Marinschek
>            Assignee: Leonardo Uribe
>             Fix For: 1.4
>
>         Attachments: jsf20upgrade.patch
>
>
> Orchestra should support JSF 2.0. The supplied patch changes the decorators in Orchestra to allow this, however, the patch is not backwards compatible with the 1.2/1.1 version (and contrary to supporting both 1.1 and 1.2 in one version, this is not possible with 2.0 anymore, as the interfaces have new methods which in turn have parameters/return types which are only available in JSF 2.0). The question will be how we will be able to continue. I see two options:
> a) a branch, and two independent releases
> b) adding a common JSF 1.2 compatibility library, which would allow to a certain extent to mimick basic JSF 2.0 infrastructure (it would not try to reimplement features from 2.0, however)
> I will also post this question to the MyFaces mailing-list, and we will see how to proceed from here.
> regards,
> Martin

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