[
https://jira.jboss.org/browse/JBAS-8683?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on JBAS-8683:
-------------------------------------
Marius, I think the spec is at least ambiguous here, and contradicts your current
implementation in a few points.
I think the terminus technicus 'container' is not well defined by the spec. At one
point it is referring to the 'runtime container' at another point it says clearly:
11.3 "The container provides a built-in bean with bean type BeanManager" Which
means (if I use the same 'only word based' interpretation strategy as you) that
there is _exactly_one_ BeanManager per container. And here lies the problem! Because in
another paragraph the spec says that we BeanManagers are _per_webapp_.
Going back to the original problem now, we could also interpret that the terminus
technicus 'container' in the spec here means the BeanManager, so _one_per_webapp_
!
Btw, having extensions detected by the BeanManager (so: per webapp) is the only scenario
which makes sense, because if the extensions are only available in (and for) the EAR libs
then no classes in any webapps WEB-INF/classes could be accessed and the whole extension
mechanism would be simply useless for EAR projects!
CDI Extensions not discovered in EAR structure
----------------------------------------------
Key: JBAS-8683
URL:
https://jira.jboss.org/browse/JBAS-8683
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Weld/CDI
Reporter: Heiko Braun
Assignee: Marius Bogoevici
Priority: Optional
Fix For: TBD
A web application contains a CDI extension shipped within WEB-INF/lib. If this web
application is packaged in an EAR, the extension will not be discovered and executed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira