[jbosstools-issues] [JBoss JIRA] (JBIDE-15518) Add to CDI model extensions provided without extension service

[Viacheslav Kabanovich (JIRA)]

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

Viacheslav Kabanovich commented on JBIDE-15518:
-----------------------------------------------

In Wildfly, class org.jboss.as.messaging.deployment.CDIDeploymentProcessor adds programmatically org.jboss.as.messaging.deployment.JMSCDIExtension instead of registering it in service javax.enterprise.inject.spi.Extension.
To treat such cases in future, we added this functionality to JBoss CDI Tools. There is automatic test case for it.
Ironically, there was no need to apply the new functionality to JMSCDIExtension, which just adds built-in bean javax.jms.JMSContext. Adding built-in beans to JBoss CDI Tools had bean already implemented in another way.

I do not know other cases of programmatical registering of CDI extensions.

> Add to CDI model extensions provided without extension service
> --------------------------------------------------------------
>
>                 Key: JBIDE-15518
>                 URL: https://issues.jboss.org/browse/JBIDE-15518
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: cdi, cdi-extensions
>            Reporter: Viacheslav Kabanovich
>            Assignee: Viacheslav Kabanovich
>             Fix For: 4.2.0.Alpha1
>
>
> CDI 1.1 specification recommends to register extensions in META-INF/services/javax.enterprise.inject.spi.Extension. However, Weld implementation and Wildfly choose to add extensions directly, without service. 
> Now we find only extensions registered in service. We have to add 'hardcoded' extensions as well.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)