We're updating the issue view to help you get more done. 

Add support for non-default deployments directory to JBoss 7.x and 7.1.x

Description

We are upgrading one of our products to run on JBoss AS 7.1.1.final executing in standalone mode. As part of this, we have chosen to define alternative deployment scanners in our standalone.xml file, like this:

1 2 3 <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> <deployment-scanner path="deploymentsgrid" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="600"/> </subsystem>

Hence the relevant application is deployed to JBOSS_HOME/standalone/deploymentsgrid instead of JBOSS_HOME/standalone/deployments.

Unforunately, Cargo assumes "deployments" is the deployment target directory and thus can't support the alternative deployment scanner we have defined. So I patched a local checkout of cargo v. 1.2.5-SNAPSHOT to enable it to deploy the cargocpc.war file to an alternative deployment directory. My plugin configuration is:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 <configuration> <wait>false</wait> <container> <containerId>jboss71x</containerId> <home> ${project.build.directory}/jbossas7</home> </container> <configuration> <home>${project.build.directory}/jbossas7/standalone</home> <properties> <cargo.jboss.configuration>standalone</cargo.jboss.configuration> <cargo.servlet.port>${grid.http.port}</cargo.servlet.port> <cargo.jvmargs>-Xmx512m ${grid.jvm.args}</cargo.jvmargs> <cargo.runtime.args>--server-config=standalone-grid.xml</cargo.runtime.args> <cargo.jboss.deployment.dir>deploymentsgrid</cargo.jboss.deployment.dir> <jboss.bind.address>0.0.0.0</jboss.bind.address> </properties> <type>existing</type> </configuration> <deployables/> </configuration

Please could this patch be committed back to the code?

Thanks,

Simon

Status

Assignee

Simon Payne

Reporter

S. Ali Tokmen

Components

Fix versions

Affects versions

1.2.4

Priority

Major