Tomcat7 failed on trigger detail page about myschedule HOT 6 CLOSED

Both myschedule-1.5.0.war and myschedule-2.1.0-SNAPSHOT2.war works on Tomcat 
6.0.33 and JbossAS 7.

This problem only occur on trigger detail page in Tomcat 7.0.21. Not sure what 
is the root cause, but it seems like it might use different JSP/EL parser and 
dislike older syntax?

I appear that JSP spec disallow the use of 'class' property access. 

When tried simple test: ${'java.lang.Integer' == java.lang.Integer.class.name}, 
Tomcat 7 throws

javax.el.ELException: The identifier [class] is not a valid Java identifier as 
required by section 1.19 of the EL specification (Identifier ::= Java language 
identifier). This check can be disabled by setting the system property 
org.apache.el.parser.SKIP_IDENTIFIER_CHECK to true.
    org.apache.el.parser.AstDotSuffix.setImage(AstDotSuffix.java:46)
    org.apache.el.parser.ELParser.DotSuffix(ELParser.java:1067)
    org.apache.el.parser.ELParser.ValueSuffix(ELParser.java:1033)
    org.apache.el.parser.ELParser.Value(ELParser.java:978)
    org.apache.el.parser.ELParser.Unary(ELParser.java:948)
    org.apache.el.parser.ELParser.Multiplication(ELParser.java:712)
    org.apache.el.parser.ELParser.Math(ELParser.java:632)
    org.apache.el.parser.ELParser.Compare(ELParser.java:444)
    org.apache.el.parser.ELParser.Equality(ELParser.java:371)
    org.apache.el.parser.ELParser.And(ELParser.java:282)
    org.apache.el.parser.ELParser.Or(ELParser.java:226)
    org.apache.el.parser.ELParser.Choice(ELParser.java:183)
    org.apache.el.parser.ELParser.Expression(ELParser.java:175)
    org.apache.el.parser.ELParser.DynamicExpression(ELParser.java:147)
    org.apache.el.parser.ELParser.CompositeExpression(ELParser.java:44)
    org.apache.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:116)
    org.apache.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:172)
    org.apache.el.lang.ExpressionBuilder.createValueExpression(ExpressionBuilder.java:217)
    org.apache.el.ExpressionFactoryImpl.createValueExpression(ExpressionFactoryImpl.java:67)
    org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:984)
    org.apache.jsp.test_jsp._jspService(test_jsp.java:77)
    org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:419)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:389)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:333)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

Looks like a solution would be perform this check on backend and save it as 
variable instead.

Fixed in 2.1.1 and 1.5.1

This issue was closed by revision 8a5074c4bbe5.

This issue was closed by revision 2e8692de1742.