You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by ji...@apache.org on 2004/04/23 14:06:53 UTC
[jira] Created: (CACTUS-104) The task don't deploy the archive if the container is already started
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-104
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-104
Summary: The <jboss3x> task don't deploy the archive if the container is already started
Type: Bug
Status: Unassigned
Priority: Major
Project: Cactus
Components:
Ant Integration
Versions:
1.5
Assignee:
Reporter: Sven Daumann
Created: Fri, 23 Apr 2004 5:06 AM
Updated: Fri, 23 Apr 2004 5:06 AM
Environment: JDK 1.4.1_01, JBoss 3.0.5
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Updated: (CACTUS-104) The task don't deploy the archive if the container is already started
Posted by "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
[jira] Resolved: (CACTUS-104) The task don't deploy the
archive if the container is already started
Posted by "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 resolved CACTUS-104.
-----------------------------------
Resolution: Invalid
Fix Version/s: 1.8
Assignee: Petar Tahchiev
I am closing this issue now, because, as Vincent stated this is a problem of Cargo now.
> 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
[jira] Updated: (CACTUS-104) The task don't deploy the archive if the container is already started
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Vincent Massol (mailto:vmassol@apache.org)
Date: Sat, 8 May 2004 9:34 AM
Changes:
Fix Version changed to 1.7
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-104?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-104
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-104
Summary: The <jboss3x> task don't deploy the archive if the container is already started
Type: Bug
Status: Unassigned
Priority: Major
Project: Cactus
Components:
Ant Integration
Fix Fors:
1.7
Versions:
1.5
Assignee:
Reporter: Sven Daumann
Created: Fri, 23 Apr 2004 5:06 AM
Updated: Sat, 8 May 2004 9:34 AM
Environment: JDK 1.4.1_01, JBoss 3.0.5
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Closed: (CACTUS-104) The task don't deploy the
archive if the container is already started
Posted by "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