A possible bug on tomcat, does it still exists in JBoss 4.2.
I'm using
servlets 2.5 jstl 1.2
jboss 4.2.3.GA
My web.xml declares i'm using servlets 2.5
I receive
type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: /index.jsp(33,3) According to TLD or attribute directive in tag file, attribute items does not accept any expressions 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:148) org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1172) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:819) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2338) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2388) org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2394) org.apache.jasper.compiler.Node$Root.accept(Node.java:489) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2338) org.apache.jasper.compiler.Validator.validate(Validator.java:1737) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178) org.apache.jasper.compiler.Compiler.compile(Compiler.java:306) org.apache.jasper.compiler.Compiler.compile(Compiler.java:286) org.apache.jasper.compiler.Compiler.compile(Compiler.java:273) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:316) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) note The full stack trace of the root cause is available in the JBossWeb/2.0.1.GA logs.
This scenario is very similar to the posted bug at apache.org
https://issues.apache.org/bugzilla/show_bug.cgi?id=40913
Is this bug resolved on embedded tomcat in Jboss 4.2.3.GA? or am I forgetting something?
Thanks in advance.