Message Title

Sascha Fröhlich commented on an issue

Thanks for the help. Maybe I am missing something: JBoss AS 7.1 ships the modules

org.hibernate.validator in version 4.2.0.Final,
javax.validation.api in version 1.0.0.GA.

As far as I understand the issue, the classloader leaks are triggered because javax.validation.api has a bug, which is fixed in version 1.1.
I don't understand how using a container managed ValidatorFactory or a custom Resolver implementation could solve this problem?

Nonetheless I tried the proposed workaround - to no avail. I replaced

                                                    <bean id="validator" class="org.springframework.validation.beanvalidation.LocalValidatorFactoryBean"/>

                                                

with

                                                    <jee:jndi-lookup id="validatorFactory" jndi-name="java:comp/ValidatorFactory" />
<jee:jndi-lookup id="validator" jndi-name="java:comp/Validator" />

but this also results in a ClassLoader leak.

Bean Validation /

BVAL-463

Add Comment

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