[weld-issues] [JBoss JIRA] Commented: (WELD-778) Weld must be able to support extension discovery in the modules of an multi-module application (EAR)

[Pete Muir (JIRA)]

    [ https://issues.jboss.org/browse/WELD-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597038#comment-12597038 ] 

Pete Muir commented on WELD-778:
--------------------------------

We can't solve this with the current SPI AFAICS. We need to completely revisit how extensions are processed. I admit that when I wrote this originally, the stuff I did with classloading/structure seemed a little bit odd, and I think I just didn't see that extensions need to be per bda and call events for any bean on extensions defined in that bda for any classes that are resolvable.

The primary issue I wanted to avoid with the previous design was that events would be called multiple times for the same bean/class on the same extension, however if we only ever call events on extensions within the bda then I think this won't be a problem.

I would propose we redesign the SPI so that loadExtensions is per BDA not per app.

> 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