[
https://issues.jboss.org/browse/CDI-346?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-346:
-----------------------------------
Agree. Plus it's also not possible in an Extension to know from which 'kind'
of bean archive the current PAT did come from. We e.g. cannot make this depending on any
previously fired ProcessModule event as CDI containers might run the discovery in parallel
threads.
If some Extension gets a PAT with a class without any scope, should it handle this class?
Well, that depends whether this BDA is an 'automatic' or a 'non-pickup'
(whatever non-intuitive wording got chosen finally) bean archive.
Unclear relation between bean discovery and @WithAnnotations
------------------------------------------------------------
Key: CDI-346
URL:
https://issues.jboss.org/browse/CDI-346
Project: CDI Specification Issues
Issue Type: Bug
Affects Versions: 1.1.PFD
Reporter: Jozef Hartinger
Assignee: Pete Muir
Fix For: 1.1.FD
{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.
• each session bean
that is not excluded from discovery.
Then, container must create an AnnotatedType representing the type and fire an event of
type ProcessAnnotatedType,
as defined in Section 11.5.6, for:
• every type discovered
• each Java class, interface or enum that must be delivered to a ProcessAnnotatedType
observer, where the event parameter
is annotated with @WithAnnotations.
{quote}
Having a class
a) in an implicit bean archive
b) outside of bean archive
that does not define a bean defining annotation and the class must be delivered to a
@WithAnnotation PAT observer method.
Should this class result in a bean definition (assuming it fulfils bean requirements)?
Would not it be easier to add the category of classes that must be delivered to
@WithAnnotations PAT observer to the implicit bean archive definition?
--
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