[
https://issues.apache.org/jira/browse/MYFACES-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835679#action_12835679
]
Jakob Korherr commented on MYFACES-2564:
----------------------------------------
I don't say we should reject older versions, I really don't!!
However a JSF 1.2 application (faces-config version="1.2") expects from its
environment that there are no integrated facelets available. JSF 1.2
applications only know JSP. To run with facelets they have to bundle
facelets-1.1.x. Thus we have to disable the integrated facelets-2 for those
applications, because that's exactly what they would expect!
Am I missing something?
> 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.
