[jboss-jira] [JBoss JIRA] Closed: (JBAS-8249) CDI Extensions must be added to DU's classloader through an integration deployer

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/browse/JBAS-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed JBAS-8249.
---------------------------

         Assignee: Pete Muir  (was: Marius Bogoevici)
    Fix Version/s:     (was: 6.0.0.Final)
       Resolution: Out of Date


David fixed up the proxies to not require this.

> CDI Extensions must be added to DU's classloader through an integration deployer 
> ---------------------------------------------------------------------------------
>
>                 Key: JBAS-8249
>                 URL: https://jira.jboss.org/browse/JBAS-8249
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Weld/CDI
>    Affects Versions: 6.0.0.M4
>            Reporter: Marius Bogoevici
>            Assignee: Pete Muir
>
> CDI integration features of the various JBoss components may use  portable extensions for interacting with the CDI container.
> Wherever that is the case, make sure that the jars containing the extensions are added to deployment unit's classloader and not to the deployer's classloader (the default), as they should effectively become parts of the application that is being deployed. 
> Also, splitting the application classes between deployers and deployment unit doesn't work with Weld 1.1's proxification mechanism. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira