[
https://issues.jboss.org/browse/CDI-351?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-351:
-------------------------------
Bill Shannon suggests setting bean discovery mode to none in bean archives with extensions
automatically.
Implicit bean archive compatibility issue
-----------------------------------------
Key: CDI-351
URL:
https://issues.jboss.org/browse/CDI-351
Project: CDI Specification Issues
Issue Type: Bug
Components: Portable Extensions
Affects Versions: 1.1.PFD
Reporter: Jozef Hartinger
Assignee: Pete Muir
Priority: Blocker
Fix For: 1.1.FD
Assume an existing extension library (CDI 1.0). This library is not deployed as a bean
archive (it does not contain beans.xml). Instead, the library contains an extension which
registers beans, interceptors, etc. using BeforeBeanDiscovery.addAnnotatedType().
With CDI 1.1 the no-bean-archive assumption no longer holds and since a scope annotation
is used somewhere in the extension, this extension is now recognized as an implicit bean
archive. That causes the discovered beans to clash with those added programatically.
*Note that it is not possible to fix this by adding beans.xml with bean-discovery-mode
set to "none". This would fix the problem in CDI 1.1 but the presence of
beans.xml would break the extension in a CDI 1.0 container*.
--
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