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

Mark Struberg (JIRA) jira-events at lists.jboss.org
Tue Apr 26 06:37:18 EDT 2011


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

Mark Struberg commented on WELD-778:
------------------------------------

> IMO this was an error in CDI
I actually don't believe this was erroneous - in fact all the other etablishec @ApplicationScoped annotations (Spring, JSF, etc) always mean the WebApplication. For 'enterprise application' wide singletons, those frameworks rely on EJBs. And imo that was also the original take of WebBeans as I saw it back in early 2008. 

So rather than re-defining @ApplicationScoped as not being WebApp centric (that would be a rather huge change in the spec!) I'd say we either introduce an own @EarScoped or just use the JSR-330 @Singleton annotation for it.

Currently doing my paperwork for the CDI EG, so we can talk over there.

LieGrue,
strub

> 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


More information about the weld-issues mailing list