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

Emmanuel Bernard (Created) (JIRA) jira-events at lists.jboss.org
Thu Oct 27 11:14:45 EDT 2011

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
             Fix For: 1.1 (Proposed)

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()
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.

    .providerResolver( myOSGiResolver )
  .configure() //we have ways to customize the ValidatorFactory further

Note that Bean VAlidation approach has another benefit, you can physically ask for a specific Bean Validation provider implementation

  .byProvider( HibernateValidator.class )
    .ignoreXmlConfiguration() //bean validation configuration
    .failSafe() //Hibernate specific configuration (type safe)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the cdi-dev mailing list