You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Ganesh Jung (JIRA)" <de...@myfaces.apache.org> on 2010/02/12 07:33:28 UTC
[jira] Reopened: (MYFACES-2543) Facelets Taglib jars are not
recognized
[ https://issues.apache.org/jira/browse/MYFACES-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ganesh Jung reopened MYFACES-2543:
----------------------------------
reasons for reopning this where discussed on the dev list:
+1 on that
Go ahead and re-open it
Sent from my iPod.
On 12.02.2010, at 06:36, Ganesh <ga...@j4fry.org> wrote:
> Leo, can you please read this again? I thought we agreed on this being a MyFaces bug. IMHO te spec is clear and I don't agree on closing the issue.
>
> From the spec (10.1.2):
>
> A decision was made early in this process to strive for backwards compatibility between the latest popular version of Facelets and Facelets in JSF 2.0. 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 "yes", Facelets in JSF 2.0 is not backwards compatibile with Facelets and such an application must continue to bundle the Facelets jar file along with the application, continue to set the Facelets configuration parameters, and also set the javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER
> <context-param> to true. Please see Section 11.1.3 "Application Configuration Parameters" for details on this
> option. Any code that extends or depends on any class in package com.sun.facelets and/or its sub-packages
> must be modified to depend on the appropriate classes in package javax.faces.webapp.vdl and/or its subpackages.
> ■ 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.
> Thankfully, most applications that use Facelets fall into the latter category, or, if they fall in the former, their dependence will easily be migrated to the new public classes.
> Can we please reopen the issue and fix it?
>
> Best regards,
> Ganesh
> Facelets Taglib jars are not recognized
> ---------------------------------------
>
> Key: MYFACES-2543
> URL: https://issues.apache.org/jira/browse/MYFACES-2543
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta
> Environment: Facelets
> Reporter: Ganesh Jung
> Assignee: Leonardo Uribe
> Fix For: 2.0.0-beta-2
>
> Attachments: MyFaces_Test.jar
>
>
> Facelets taglibs defined according to the spec 10.3.2 are not recognized.
> This page uses a test taglib (see attachment):
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:test="http://j4fry.org/test">
> <body>
> <test:button />
> </body>
> </html>
> but test:button is not resolved...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.