[
https://issues.apache.org/jira/browse/MYFACES-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835775#action_12835775
]
Ganesh Jung commented on MYFACES-2564:
--------------------------------------
Which faces-configs do you check to decide whether facelets are disabled? There
might be a few via the web.xml context param and some more with each jar on the
classpath. Will facelets be disabled if any of the faces-configs is below 2.0?
I don't think it would be ok to disable facelets, just because a jar containing
some old faces-config is dropped on the classpath.
My concern is to have only one version of dojofaces.jar for JSF 1.1, 1.2 and
2.0 with RI as well as with MyFaces. The jar has got a faces-config 1.1 to
define some managed beans, but it needs facelets to run the contained xhtmls.
I've tested with Mojarra 2.0 since early beta and it always worked fine with
integrated JSF 2.0 facelets.
And again the other question: What could be the possible use of an algorithm
beyond the context-param that disables facelets?
> 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.
