[cdi-dev] [JBoss JIRA] (CDI-372) clarify behaviour of implicit bean archive

Antoine Sabot-Durand (JIRA) issues at jboss.org
Mon Mar 24 10:59:13 EDT 2014


     [ https://issues.jboss.org/browse/CDI-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Sabot-Durand reassigned CDI-372:
----------------------------------------

    Assignee: Antoine Sabot-Durand

    
> clarify behaviour of implicit bean archive
> ------------------------------------------
>
>                 Key: CDI-372
>                 URL: https://issues.jboss.org/browse/CDI-372
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Packaging and Deployment
>    Affects Versions: 1.1.PFD
>            Reporter: David Konecny
>            Assignee: Antoine Sabot-Durand
>            Priority: Minor
>              Labels: CDI_spec_chge
>             Fix For: 1.2 Proposed
>
>
> I read chapter "12.1 Bean archives" which defines 'explicit bean archive' and 'implicit bean archive' and following that I removed beans.xml from my existing application only to find out that deployment of my app now fails because of unsatisfied dependencies. It took me a while to figure out the problem: there is behavioural difference between explicit and implicit bean archive which is mentioned later in the middle of chapter "12.4 Bean discovery":
> The container discovers:
> • each Java class, interface or enum deployed in an explicit bean archive, and
> • each Java class interface, or enum with a bean defining annotation in an implicit bean archive.
> The fact that implicit bean archive provides only beans with defining annotations is very important piece of information and I would like to suggest to mention that early in chapter 12.1 when the bean archive concepts are defined. Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the cdi-dev mailing list