The <jboss3x> task don't deploy the archive if the container is already started

• Key: CACTUS-104
• Type: Bug
• Status: Closed
• Resolution: Invalid
• Priority: Major
• Assignee: Petar Tahchiev
• Reporter: Sven Daumann
• Component/s: Ant Integration
• Affects Version/s: 1.5
• Fix Version/s: 1.8

Description

When the JBoss container was already started the cactus task don't deploy the ear to the JBoss deploy directory.

The deployment works, when the cactus task start the JBoss container, the task deploy the archive to the JBoss directory.

I look into the source code, the deployment occur in the prepare method of the JBoss3xContainer class. The prepare method is called from the startup method of the same class. I see in the ContainerRunner class the startupContainer method, which check if the container is running.
So the prepare method is only called, if the container is not running.

JBoss comes with a hot deployment, I don't need the container startup and shutdown from the cactus task.

Comments

[Vincent Massol]

Sven, you're right, this isn't suported in Cactus. We're now migrating to Cargo (http://cargo.codehaus.org) so this issue will be solved in Cargo land. Thanks.

[Petar Tahchiev]

I am closing this issue now, because, as Vincent stated this is a problem of Cargo now.