Re: Problem with JBoss 7.1. Standalone

Hi Dirk

This is a known issue and will be fixed with version 1.2.1: https://jira.codehaus.org/browse/CARGO-1086

If you wish, you can use version 1.2.1-SNAPSHOT, instructions on http://cargo.codehaus.org/Maven2+Plugin+Installation#snapshots

Cheers

S. Ali Tokmen
http://ali.tokmen.com/

GSM (ch): +41 79 207 29 22 [Swisscom]
GSM (fr): +33 7 70 10 33 79 [Virgin Mobile]
GSM (tr): +90 555 266 52 73 [Avea]

My AIM, ICQ, MSN Messenger and Yahoo IM
contact details are on http://contact.ali.tokmen.com

On 2012/02/21 10:43, Dirk Mahler wrote:

Hi,

we're setting up a project which uses JBoss 7.1.0.Final as container. Therefore we created a standalone configuration using cargo, which correctly installs the container but fails on startup with the following message:

[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.0:run (default-cli) on project cargo.jboss71: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.0:run failed: Cannot modify XML file C:\temp\cargo.jboss71.test\target\cargo\configurations\jboss71x/configuration/standalone.xml: Node //server/socket-binding-group/socket-binding[@name='jmx-connector-registry'] not found in file C:\temp\cargo.jboss71.test\target\cargo\configurations\jboss71x/configuration/standalone.xml -> [Help 1]

It seems that cargo tries to change a node in the JBoss descriptor which does not exist. Currently we implemented a workaround by providing a standalone.xml which contains the missing information.

The problem can be reproduced by running "mvn install cargo:run" using the attached pom.xml.

Regards

Dirk

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email