[arquillian-issues] [JBoss JIRA] Updated: (ARQ-349) Create a Protocol processor SPI for modifying the final deployment generated by the DeploymentPackager

[Aslak Knutsen (JIRA)]

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

Aslak Knutsen updated ARQ-349:
------------------------------

    Fix Version/s: 1.0.0.Alpha5
                       (was: 1.0.0.Beta1)


> Create a Protocol processor SPI for modifying the final deployment generated by the DeploymentPackager 
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ARQ-349
>                 URL: https://issues.jboss.org/browse/ARQ-349
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Packaging Enricher SPI
>            Reporter: Aslak Knutsen
>             Fix For: 1.0.0.Alpha5
>
>
> In some cases we need to modify the Protocol generated Deployment. 
> In the case of CDI, it's BeanManagers are hierarchical, a BeanManager created for a ejb-jar in a ear is not visible to a war unless the war also contains a beans.xml. When using the Servlet Protocol, a war is added without a beans.xml since the protocol it self is unaware of CDI, and Beans are never injected into the testcase.
> DeploymentProcessor.process(TestClass relevant class, TestDeployment auxAndApplicationArchives, Archive<?> finalDeployment);
> https://issues.jboss.org/browse/WELD-709

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira