Specifiying tag library only by URI picks wrong JSTL core tld ------------------------------------------------------------- Key: JBAS-4315 URL: http://jira.jboss.com/jira/browse/JBAS-4315 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.2.0.CR1 Reporter: Wolfgang Knauf Assigned To: Remy Maucherat I built a web app (spec 2.5) with JSTL usage. I included the JSTL with these two steps: 1) added jstl.jar from server\default\deploy\jboss-web.deployer to WEB-INF\lib 2) added this to my JSP page: <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> I did not add c.tld file to WEB-INF, and I did not add a jsp-config element to web.xml. I add this to the JSP: <c:out test="${sessionScope.someVariable}"></c:out> This results in a JSP compilation error: org.apache.jasper.JasperException: /index.jsp(14,0) According to the TLD or the tag file, attribute value is mandatory for tag out org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:802) ... I finally found that JBoss resolves "c-1_0.tld" which does not allow "rtexprvalue". The problem is that "c.tld" and "c-1_0.tld" have the same URI. I think JBoss should look for the highest version matching the requesting web app. Eclipse WTP 1.5 seems to do this the right way because I do not receive validation errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira