]
Pete Muir commented on CDI-345:
-------------------------------
I suspect we then need to back out this part of the change, and just do this for all scope
types.
Bean defining annotation (as currently specified) cannot be used for
bean discovery
-----------------------------------------------------------------------------------
Key: CDI-345
URL:
https://issues.jboss.org/browse/CDI-345
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
{quote}Any scope type, which *has an associated context* (as defined in Chapter 6), is a
bean defining annotation{quote}
{quote}First the container must discover types. 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.
{quote}
The set of context cannot be enumerated until the AfterBeanDiscovery phase in which
extensions register contexts. This creates a chicken-egg problem.
--
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: