[
https://issues.jboss.org/browse/WELD-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596845#comment-12596845
]
Marius Bogoevici commented on WELD-778:
---------------------------------------
A few points to consider when investigating this issue:
1. Extensions are loaded via
org.jboss.weld.bootstrap.WeldBootstrap#loadExtensions(Classloader), so an
integrator would have to call this multiple times, making sure that extensions
are not duplicated (i.e. extensions visible to both a module and submodule CL
are processed only once)
2. org.jboss.weld.bootstrap.ExtensionBeanDeployer#deployBeans() is using the
Container ClassTransformer - again, extensions in sub-modules will not be
visible
Generally speaking, the extension processing model is taking place at
deployment level, but could allow for more granular processing.
> 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
