[ 
https://issues.apache.org/jira/browse/MYFACES-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835817#action_12835817
 ] 

Michael Concini commented on MYFACES-2564:
------------------------------------------

I can certainly agree with that Leonardo.  We could certainly use MYFACES-2543 
for hashing out the overarching facelets 1.x migration strategy since there has 
already been much active discussion around it.  

It doesn't really matter to me whether we maintain these as two separate issues 
or if we consolidate this issue into  2543 as long as we ensure that they are 
both handled.  I'll defer to those who have been involved in the community 
longer than I as to how these types of situations have typically been handled.  

> facelets in an app with a 1.2 level faces-config do not work
> ------------------------------------------------------------
>
>                 Key: MYFACES-2564
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2564
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta
>            Reporter: Michael Concini
>            Assignee: Michael Concini
>
> According to section 10.1.2 of the spec:
> The sole determinant to backwards compatibility lies in the answer to the 
> question, "is there any Java
> code in the application, or in libraries used by the application, that 
> extends from or depends on any class in package
> com.sun.facelets and/or its sub-packages?"
> ...
> If the answer to this question is "no", Facelets in JSF 2.0 is backwards 
> compatible with pre-JSF 2.0 Facelets and such
> an application must not continue to bundle the Facelets jar file along with 
> the application, and must not continue to set
> the Facelets configuration parameters.
> This implies that simply removing the pre-2.0 facelets bundle should allow 
> the app to run properly again in a 2.0 runtime.  
> The problem is that right now we're doing a check against the version in the 
> faces-config in addition to checking for the context param and the 
> availability of the com/sun/facelets classes.  We should only be doing the 
> latter, as the version in the faces-config should only be used for schema 
> validation.

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

Reply via email to