|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
10/Mar/08 07:55 PM
|
|
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.
|
|
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. |
Show » |
| There are no subversion log entries for this issue yet.
|
|
Bug
Closed
Major
The <jboss3x> task don't deploy the archive if the container is already started
