[cdi-dev] [JBoss JIRA] (CDI-579) Extension disqualifies a jar as 'implicit bean archive'?

Romain Manni-Bucau (JIRA) issues at jboss.org
Mon Jan 25 11:45:01 EST 2016


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

Romain Manni-Bucau commented on CDI-579:
----------------------------------------

[~emilyj] how many users application did you see relying on this? Encountered this issue 4 times and each time the fix has been the same whoever lead it. Changing something not used or wrong is fine, even for specs, it is done in most new versions actually.

> Extension disqualifies a jar as 'implicit bean archive'?
> --------------------------------------------------------
>
>                 Key: CDI-579
>                 URL: https://issues.jboss.org/browse/CDI-579
>             Project: CDI Specification Issues
>          Issue Type: Bug
>            Reporter: Mark Struberg
>            Priority: Minor
>
> The bean-discovery-wording is a bit odd. 
> This has been in since CDI-1.1
> {code}
> An archive which:
> • contains a beans.xml file with the bean-discovery-mode of none, or,
> • contains an extension and no beans.xml file is not a bean archive.
> is not a bean archive.
> {code}
> That means even if you have an @ApplicationScoped MyService class in a jar which has a single CDI Extension then this MyServices will *not* get picked up as CDI bean? At least according to this wording?
> Feels mega-weird to me and might conflict with the implicit beans archive definition a few lines below.
> I'm pretty sure in OWB we will pick those beans up. How does Weld behave?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the cdi-dev mailing list