FYI, it looks like the Jetty folks have addressed the problem of not
completely recognizing TLDs embedded in a JAR file. Now we can go back and
validate Shale behavior in that environment too.
Craig
---------- Forwarded message ----------
From: Jan Bartel (JIRA) <[EMAIL PROTECTED]>
Date: Dec 8, 2006 5:51 AM
Subject: [jira] Resolved: (JETTY-170) Jetty violates the JSP specification
regarding recognizing TLDs embedded in a JAR file
To: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/JETTY-170?page=all ]
Jan Bartel resolved JETTY-170.
------------------------------
Resolution: Fixed
Fix Version/s: 6.1.0rc0
Updated to glassfish build SJSAS-9_1-B27-EA-07_Dec_2006 which fixes this
problem.
Jetty violates the JSP specification regarding recognizing TLDs embedded
in a JAR file
--------------------------------------------------------------------------------------
Key: JETTY-170
URL: http://jira.codehaus.org/browse/JETTY-170
Project: Jetty
Issue Type: Bug
Components: JSP
Affects Versions: 6.0.1
Reporter: Craig McClanahan
Assigned To: Jan Bartel
Fix For: 6.1.0rc0
Section JSP.7.2.1 of the JSP 2.1 specification requires that JSP
containers recognize TLD files that are embedded in the META-INF directory
of a JAR file that is contained in the WEB-INF/lib directory. Jetty is not
recognizing such a TLD in the case of the MyFaces 1.1 implementation JAR (
myfaces-impl-1.1.4.jar), even though the error message that you receive
implies that the JAR files have been checked.
An example of this problem is described by a thread on the jetty-support
mailing list at <
http://www.nabble.com/-Jetty-support--Jetty-6-and-JSF-taglibs-problems-t2613645.html
.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
