Uploaded image for project: 'Codehaus Cargo'
  1. CARGO-1141

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

    Details

    • Type: Improvement
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 1.2.4
    • Fix versions: 1.3.0
    • Components: JBoss
    • Labels:
      None
    • Environment:

      Encountered on Windows 7 (x64) with JDK 1.6.0 update 29 and Maven 3.0.3.

      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:

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

      <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

        Attachments

          Activity

            People

            • Assignee:
              simonpayne Simon Payne (Inactive)
              Reporter:
              alitokmen S. Ali Tokmen
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: