David Jencks wrote:
I don't know what you mean. Can you give a specific example?
The example Rod gave of an ejb.jar deployment being stopped by shutting
down the ejb container is an example.
Again, I don't have any idea what you mean and an example would be very
helpful.
Personally, I think
The whole service life-cycle, deployer, dependency management layer
needs to
be rethought to come up with a more coherent behavior. Right now there
are too
many ways a collection of components can be brought into the server and
insufficient
knowledge of how this was done to allow
On Friday, July 11, 2003, at 01:29 PM, Scott M Stark wrote:
The whole service life-cycle, deployer, dependency management layer
needs to
be rethought to come up with a more coherent behavior. Right now there
are too
many ways a collection of components can be brought into the server
and
just 0s 1s -
the trick is getting them lined up in the proper order
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 1:54 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] multiple deployment info entries for
invoker.war
:35 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] multiple deployment info entries for
invoker.war
The bigger problem is that the deployment layer does not run
a clean state
machine. Requests to deploy content should not be allowed
when the MainDeployer
is being shutdown
Theoretically, but a problem with not using the MainDeployer.shutdown is that
the deployment shutdown order will change since the MainDeployer.removeDeployer
method is not iterating over the deploymentList in reverse order as is the case
for MainDeployer.shutdown. If this is corrected then the
:[EMAIL PROTECTED]
Sent: Friday, July 04, 2003 9:35 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] multiple deployment info entries for
invoker.war
The cause of this is logic in MainDeployer.addDeployer to attempt
to deploy any waitingDeployments entries. The invoker.war is deployed
The bigger problem is that the deployment layer does not run a clean state
machine. Requests to deploy content should not be allowed when the MainDeployer
is being shutdown and therefore the deployment list copy is not needed.
Adding a removeDeployer loop in the MainDeployer.shutdown actually
The cause of this is logic in MainDeployer.addDeployer to attempt
to deploy any waitingDeployments entries. The invoker.war is deployed
before there is a WAR deployer and as new deployers are added an attempt
is made to reprocess the invoker.war. The MainDeployer.init most likely
needs to be
