Hi Gunnar, Where are you seeing the failures? Can you point us to the stacktrace? -Jaikiran On Tuesday 09 April 2013 06:59 PM, Gunnar Morling wrote:

The implementation class, org.apache.el.ExpressionFactoryImpl, can be found in: module: org.jboss.as.web jar: modules/system/layers/base/org/jboss/as/web/main/jbossweb-7.2.0.Final.jar Note for EL 3.0, this implementation class may change: https://issues.jboss.org/browse/JBEE-133 Shelly ----- Original Message ----- From: "Gunnar Morling" <gunnar(a)hibernate.org&gt; To: jpai(a)redhat.com Cc: jboss-as7-dev(a)lists.jboss.org Sent: Tuesday, April 9, 2013 11:34:36 AM Subject: Re: [jboss-as7-dev] Module for EL Jaikiran, The test is org.jboss.as.test.integration.jpa.beanvalidation.beanvalidationinheritancetest.BeanValidationJPAInheritanceTestCase, you can find the complete stack trace at http://pastebin.com/B6t7t58N . Note that I had to modify the test in order to get the original exception (the test makes an assertion on the stack trace). The root cause of the exception is that no EL implementation can be found. This failure originates from a build for my PR for AS7-6665 [1], which has several other test failures as well, which I'm going through atm. At least the JAX-RS ones are caused by the removal of a previously existing interface in HV 5. Thanks, --Gunnar [1] http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/6706 2013/4/9 Jaikiran Pai < jpai(a)redhat.com > Hi Gunnar, Where are you seeing the failures? Can you point us to the stacktrace? -Jaikiran On Tuesday 09 April 2013 06:59 PM, Gunnar Morling wrote: Hi all, I'm currently working on updating the AS module for Hibernate Validator to the latest release (HV 5.x, Bean Validation 1.1, see [1]). As of this release, Hibernate Validator has a new dependency to the Unified EL. So I have added this to the HV module descriptor: <module name="javax.el.api"/> Based on test failures I'm seeing ("javax.el.ELException: Provider org.apache.el.ExpressionFactoryImpl not found"), I think I need to add a dependency for the actual EL implementation as well. I don't know though which module that would be. Does anyone know which is the right one or has an example of other modules depending on EL? Thanks, --Gunnar [1] https://issues.jboss.org/browse/AS7-6665 _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Thanks to Scott's help, I think I understood the details a bit more. HV uses javax.el.ExpressionFactory/FactoryFinder which in turn uses the TCCL to find implementations and cache it in FactoryFinderFache. For WAR deployments, the cache is pre-populated by ELExpressionFactoryProcessor with the implementation from the web module mentioned by Shelly. As this is not the case for other deployment types (e.g. RARs), tests using HV based on such deployment types fail with the exception. So I think a separate EL module (upon which HV could depend, independently from the current deployment type) would indeed make sense. --Gunnar 2013/4/9 Scott Marlow <smarlow(a)redhat.com&gt;

On 04/15/2013 01:21 PM, Hardy Ferentschik wrote: Yes, it is actively maintained. It lives in the Jasper impl of web (and undertow), which is in turn now synced with upstream Tomcat EL. For the EL3 implementation, the decision hasn't been made yet besides using either one from Tomcat (there's none at the moment) or the RI. Rémy