I had a closer look now. There is actually two issues here:
EL 2.1 doesn't have a portable way for retrieving an ExpressionFactory
EL 2.1 doesn't support method invocations
While I think we could find ways to work around #1 (e.g. by emulating the behavior of ExpressionFactory#newInstance() from EL 2.2 ourselves or offering an API on HibernateValidatorConfiguration to pass the EL factory), I don't see a viable solution to address #2 (method invocation is used for formatting purposes).
One possible improvement could be to make EL not required in cases where it is not used, which would make HV 5 run on Tomcat 6 as long as no EL messages are used. But we've had this discussion before and couldn't agree to implement this.
So I think at this point the only solution is to replace the EL JARs in $CATALINA_HOME/lib. For the Maven Tomcat plug-in you probably could exclude the EL 2.1 dependencies from the plug-in and add an EL 2.2 implementation as plug-in dependency instead.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
I had a closer look now. There is actually two issues here:
While I think we could find ways to work around #1 (e.g. by emulating the behavior of ExpressionFactory#newInstance() from EL 2.2 ourselves or offering an API on HibernateValidatorConfiguration to pass the EL factory), I don't see a viable solution to address #2 (method invocation is used for formatting purposes).
One possible improvement could be to make EL not required in cases where it is not used, which would make HV 5 run on Tomcat 6 as long as no EL messages are used. But we've had this discussion before and couldn't agree to implement this.
So I think at this point the only solution is to replace the EL JARs in $CATALINA_HOME/lib. For the Maven Tomcat plug-in you probably could exclude the EL 2.1 dependencies from the plug-in and add an EL 2.2 implementation as plug-in dependency instead.