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

["Petar Tahchiev (JIRA)" <ca...@jakarta.apache.org>]

     [ https://issues.apache.org/jira/browse/CACTUS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Petar Tahchiev closed CACTUS-104.
---------------------------------


> The <jboss3x> task don't deploy the archive if the container is already started
> -------------------------------------------------------------------------------
>
>                 Key: CACTUS-104
>                 URL: https://issues.apache.org/jira/browse/CACTUS-104
>             Project: Cactus
>          Issue Type: Bug
>          Components: Ant Integration
>    Affects Versions: 1.5
>         Environment: JDK 1.4.1_01, JBoss 3.0.5
>            Reporter: Sven Daumann
>            Assignee: Petar Tahchiev
>             Fix For: 1.8
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


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