[arquillian-issues] [JBoss JIRA] Commented: (ARQ-205) Redesign packaging

[Dan Allen (JIRA)]

    [ https://jira.jboss.org/browse/ARQ-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12538032#action_12538032 ] 

Dan Allen commented on ARQ-205:
-------------------------------

Just for reference, this affects the jetty-embedded-6_1 and tomcat-embedded-6 containers atm. I put in a "workaround" for this problem in jetty-embedded-6_1 since it supports a secondary web.xml file, but there is no such thing for tomcat. But we don't want that approach anyway. Just noting the current state of affairs.

> Redesign packaging
> ------------------
>
>                 Key: ARQ-205
>                 URL: https://jira.jboss.org/browse/ARQ-205
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Packaging Enricher SPI, Test Protocol SPIs and Implementation
>            Reporter: Aslak Knutsen
>            Assignee: Aslak Knutsen
>             Fix For: 1.0.0.Alpha3
>
>
> In the current version the Packager is responsible for creating the final deployment and adding the Protocol as just another AuxiliaryArchive. The problem here is that the Packager has to know about which Protocol is running and pack differently based on it. e.g. when using a Servlet protocol it has to be a WebArchive in the deployment. 
> Since the protocol has the information on how it needs to package itself and where to place the auxiliary archives in relation to itself the Protocol should do the final packaging.
> Remove the Packager SPI and add a new ProtocolPackager SPI on Protocol level.
> Each protocol now knows how it needs to modify the Deployment to communicate with it.

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