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

[Jason Greene (JIRA)]

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

Jason Greene reopened JBAS-8249:
--------------------------------



Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them.

Future releases beyond 6.1 can be done provided a community member steps up to coordinate them.

> CDI Extensions must be added to DU's classloader through an integration deployer 
> ---------------------------------------------------------------------------------
>
>                 Key: JBAS-8249
>                 URL: https://issues.jboss.org/browse/JBAS-8249
>             Project: Legacy JBoss Application Server 6 
>          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.
For more information on JIRA, see: http://www.atlassian.com/software/jira