[hibernate-issues] [Hibernate-JIRA] Assigned: (HV-363) HV uses Thread's context class loader to load internal implementation classes

HV uses Thread's context class loader to load internal implementation classes ----------------------------------------------------------------------------- Key: HV-363 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-363 Project: Hibernate Validator Issue Type: Bug Components: engine Reporter: Sanjeeb Sahoo Assignee: Kevin Pollet Priority: Blocker Fix For: 4.2.0 {{org.hibernate.validator.engine.resolver.DefaultTraversableResolver}} uses Thread's context class loader to load {{JPA_AWARE_TRAVERSABLE_RESOLVER_CLASS_NAME}}, which is {{org.hibernate.validator.engine.resolver.JPATraversableResolver}}. Why? Since one implementation class is looking for another implementation class, should it not use {{getClass().getClassLoader()}} instead? The relevant code is given below: {code} private void detectJPA() { try { loadClass( PERSISTENCE_UTIL_CLASS_NAME, this.getClass() ); log.debug( "Found {} on classpath.", PERSISTENCE_UTIL_CLASS_NAME ); } catch ( ValidationException e ) { log.debug( "Cannot find {} on classpath. All properties will per default be traversable.", PERSISTENCE_UTIL_CLASS_NAME ); return; } try { @SuppressWarnings( "unchecked" ) Class<? extends TraversableResolver> jpaAwareResolverClass = (Class<? extends TraversableResolver>) loadClass(JPA_AWARE_TRAVERSABLE_RESOLVER_CLASS_NAME, this.getClass() ); NewInstance<? extends TraversableResolver> newInstance = NewInstance.action( jpaAwareResolverClass, "" ); if ( System.getSecurityManager() != null ) { jpaTraversableResolver = AccessController.doPrivileged( newInstance ); } else { jpaTraversableResolver = newInstance.run(); } log.info( "Instantiated an instance of {}.", JPA_AWARE_TRAVERSABLE_RESOLVER_CLASS_NAME ); } catch ( ValidationException e ) { log.info( "Unable to load or instanciate JPA aware resolver {}. All properties will per default be traversable.", JPA_AWARE_TRAVERSABLE_RESOLVER_CLASS_NAME ); } } {code}