[cdi-dev] [JBoss JIRA] (CDI-632) Possible conflict for Implicit bean archive definition between core and SE

Stephan Knitelius (JIRA) issues at jboss.org
Fri Sep 16 12:58:00 EDT 2016

    [ https://issues.jboss.org/browse/CDI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294677#comment-13294677 ] 

Stephan Knitelius commented on CDI-632:

I am not a fan of implicit bean archives, but wouldn't it be better if SE worked the same?

> Possible conflict for Implicit bean archive definition between core and SE
> --------------------------------------------------------------------------
>                 Key: CDI-632
>                 URL: https://issues.jboss.org/browse/CDI-632
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Java SE Integration
>    Affects Versions: 2.0-EDR2
>            Reporter: Antoine Sabot-Durand
>            Priority: Minor
> Section 12.1 (which should be satisfied in SE an EE) states:
> bq. An implicit bean archive is any other archive which contains one or more bean classes with a bean defining annotation as defined in Bean defining annotations.
> And section 15.1 reads:
> {quote}When running in Java SE, the container must extend the rules defined in Bean archives and also ensure that :
> An archive which doesn’t contain a beans.xml file can’t be discovered as an implicit bean archive unless:
> * the application is launched with system property javax.enterprise.inject.scan.implicit set to true, or
> * the container was initialized with a parameter map containing an entry with javax.enterprise.inject.scan.implicit as key and Boolean.TRUE as value.{quote}
> Perhaps this deserve a bit of clarification.

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list