[
https://issues.jboss.org/browse/WELD-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597730#comment-12597730
]
Pete Muir commented on WELD-778:
--------------------------------
Hi Mark, thanks for clarifying. To be pedantic, Java EE does define some
classloading visibility rules, however it only defines a minimum set of
requirements, not a full system. Can you explain in more detail how the bean
archive definition relies on "such things" - best is if you can can quote
sentences you think need cleaning up. We can then do this no problem in CDI 1.1
Now I understand about what you mean about the "what does application mean" -
and your point makes sense. Suggest you raise a CDI issue for this and include
that quote in it. IMO this was an error in CDI, it needs to mention the Java EE
spec here too, but we can debate that on the EG.
> Weld must be able to support extension discovery in the modules of an
> multi-module application (EAR)
> ----------------------------------------------------------------------------------------------------
>
> Key: WELD-778
> URL: https://issues.jboss.org/browse/WELD-778
> Project: Weld
> Issue Type: Feature Request
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.0.Beta2
> Reporter: Marius Bogoevici
> Fix For: TBC
>
>
> Currently, only extensions which are visible to the entire application (i.e.
> all modules) are installed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
