[#CACTUS-104] The <jboss3x> task don't deploy the archive if the container is already started

Cactus

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

Created: 23/Apr/04 12:06 PM Updated: 11/Apr/08 12:36 PM

Return to search

Component/s:

Ant Integration

Affects Version/s:

1.5

Fix Version/s:

1.8

Time Tracking:

Not Specified

Environment:

JDK 1.4.1_01, JBoss 3.0.5

Issue Links:

dependent

This issue depends upon:

~~CACTUS-151~~ Refactor Ant integration to use Cargo

Resolution Date:

10/Mar/08 07:55 PM

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Vincent Massol made changes - 08/May/04 04:34 PM

Field	Original Value	New Value
Fix Version/s		1.7 [ 10693 ]

Vincent Massol made changes - 11/Nov/04 11:30 AM

Link

This issue depends upon ~~CACTUS-151~~ [ ~~CACTUS-151~~ ]

Vincent Massol made changes - 28/Jan/05 06:13 AM

Fix Version/s

1.7 [ 10693 ]

Petar Tahchiev made changes - 10/Mar/08 07:55 PM

Resolution		Invalid [ 6 ]
Fix Version/s		1.8 [ 12310167 ]
Status	Open [ 1 ]	Resolved [ 5 ]
Assignee		Petar Tahchiev [ paranoiabla ]

Petar Tahchiev made changes - 11/Apr/08 12:36 PM

Status

Resolved [ 5 ]

Closed [ 6 ]