[cdi-dev] [JBoss JIRA] (CDI-184) Make sure that CDI.current() works in a modular environment

Make sure that CDI.current() works in a modular environment ----------------------------------------------------------- Key: CDI-184 URL: https://issues.jboss.org/browse/CDI-184 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Emmanuel Bernard Assignee: Pete Muir Fix For: 1.1.PRD OSGi containers and other modular environments tend to hide service files and consider them implementation details. That means that a naive current classloader based implementation won't discover the various CDI implementations. There are several approaches to try and work around this problem in EE specs h4. JPA 2's approach JPA 2 does have a static getter / setter pair {code}PersistenceProviderResolverHolder.getPersistenceProviderResolver() PersistenceProviderResolverHolder.setPersistenceProviderResolver(){code} which holds the resolver to use. A modular environment is free to override the default resolver. h4. Bean Validation's approach Bean Validation uses a different approach to work around the nasty static field. {code} Validation .byDefaultProvider() .providerResolver( myOSGiResolver ) .configure() //we have ways to customize the ValidatorFactory further .buildValidatorFactory(); {code} Note that Bean VAlidation approach has another benefit, you can physically ask for a specific Bean Validation provider implementation {code} Validation .byProvider( HibernateValidator.class ) .configure() .ignoreXmlConfiguration() //bean validation configuration .failSafe() //Hibernate specific configuration (type safe) .buildValidatorFactory(); {code}