[jira] Updated: (CACTUS-104) The task don't deploy the archive if the container is already started

["Vincent Massol (JIRA)" <ca...@jakarta.apache.org>]

     [ http://issues.apache.org/jira/browse/CACTUS-104?page=history ]

Vincent Massol updated CACTUS-104:
----------------------------------

    Fix Version:     (was: 1.7)

> The <jboss3x> task don't deploy the archive if the container is already started
> -------------------------------------------------------------------------------
>
>          Key: CACTUS-104
>          URL: http://issues.apache.org/jira/browse/CACTUS-104
>      Project: Cactus
>         Type: Bug
>   Components: Ant Integration
>     Versions: 1.5
>  Environment: JDK 1.4.1_01, JBoss 3.0.5
>     Reporter: Sven Daumann

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

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org