[arquillian-issues] [JBoss JIRA] Updated: (ARQ-363) Create a separate Arquillian Deployer war for JBoss AS Servers

[ https://issues.jboss.org/browse/ARQ-363?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-363: ------------------------------ Description: The JBoss AS Client lib has a dependency set of 249 libs that blow up on windows machines where classpath length is a issue. ProfileService Management View only expose parts of the info we need, so to reliably deploy and introspect our deployments we need to create our own little WAR that can do the following: - Act as a Rest like Deployer / UnDeployer -- this will remove the need for a client api all together - Hook into the JBoss AS internal deployer chain and extract as much info about the deployment as possible -- servlets - classes, mappings, contexts -- ejbs - classes, interfaces, remote, local, jndi names -- ws - end points etc The metadata will be used by the Protocols to find where to do the test invocation, client and incontainer @EJB enrichment, Servlet URL enrichment, etc.. was: The JBoss AS Client lib has a dependency set of 249 libs that blow up on windows machines where classpath length is a issue. ProfileService Management View only expose parts of the info we need, so to reliably deploy and introspect our deployments we need to create our own little WAR that can do the following: - Act as a Rest like Deployer / UnDeployer - this will remove the need for a client api all together - Hook into the JBoss AS internal deployer chain and extract as much info about the deployment as possible - servlets - classes, mappings, contexts - ejbs - classes, interfaces, remote, local, jndi names - ws - end points etc The metadata will be used by the Protocols to find where to do the test invocation, client and incontainer @EJB enrichment, Servlet URL enrichment, etc.. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira