[jboss-jira] [JBoss JIRA] Commented: (JBAS-8106) Move MC/Weld deployer into AS

[Kabir Khan (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12535934#action_12535934 ] 

Kabir Khan commented on JBAS-8106:
----------------------------------

One issue that needs looking into is that currently the Mc->Weld tests that have the "main" Weld bean implemented as an EJB (but rather as a Managed Bean) fail. This is currently worked around by including a dummy KickstartEJB whose only job is to be there to initialise the EJB dependencies when the BootstrapBean calls DynamicDependencyCreator.createDependencies() on Start.

> Move MC/Weld deployer into AS
> -----------------------------
>
>                 Key: JBAS-8106
>                 URL: https://jira.jboss.org/browse/JBAS-8106
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>            Reporter: Kabir Khan
>            Assignee: Kabir Khan
>             Fix For: 6.0.0.M4
>
>
> Since the rest of weld-int (JBAS-7938) now lives in AS, this lives here too now.
> Until this feature is final, all jars are in weld.deployer, but it is disabled. To enable, uncomment this part of weld-deployers-jboss-beans.xml
>   <!--  UNCOMMENT THIS TO ENABLE WELD/MC INJECTION - This feature is currently very experimental and so not enabled by default  -->
>   <!-- Adds plugin to BeanMetaDataDeployer that installs WeldKernelControllerContexts -->
>   <!-- bean name="WeldBeanMetaDataDeployerPlugin" class="org.jboss.weld.integration.deployer.mc.WeldBeanMetaDataDeployerPlugin"/ -->  

-- 
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