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

Ganesh Jung commented on MYFACES-2543:
--------------------------------------

Now that the spec issue is solved here's my suggestion to treat this issue: 
MyFaces shouldn't make any distinction between 
http://java.sun.com/dtd/facelet-taglib_1_0.dtd taglibs and 
http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd taglibs.

Trying to craft an algorithm that distinguishes between "good taglibs" and "bad 
taglibs" will unerringly fail in some cornercases. A jar may contain some 
com.sun.facelets classes or some java taghandlers, but the defined tags never 
use them. Or maybe the developer knows how to call the tags so that the legacy 
code doesn't run.

Nobody will blame MyFaces for ClassNotFoundExceptions when stumbling onto a 
com.sun.facelets reference, but MyFaces will be blamed if fully functional 
taglibs don't run because of some heuristic jar scanning that MyFaces does at 
startup.

> 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
>         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.

Reply via email to