Could you please show the exception you are seeing in the log. This will help me
1. understand without having to reproduce the problem what you are writing about. 2. If I do attempt to reproduce the problem, indicate to me that I have found the same problem you are working with. Have you seen this problem with any .ears from the testsuite? Thanks david jencks On 2002.03.18 08:35:57 -0500 Vesco Claudio wrote: > If you try to make the deploy of a ear, then you make the undeploy and > therefore you make the deploy of the same one ear, comes written in log > one exception. > > In this moment, I don't have the possibility to give you a better > example, but I think you can reproduce the exception with the above > operations. > > I think that the problem is that in the management of the resources > jsr77 it does not come created the resource before father but tries to > create the dependent resources. > > With the changed order, the exception does not happen. > > The proposed resolution does not resolve the problem discussed in the > maillist, but resolves an other problem. > > Claudio > > > -----Original Message----- > > From: David Jencks [SMTP:[EMAIL PROTECTED]] > > Sent: Monday, March 18, 2002 1:51 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-dev] Ordering part 2 :-) > > > > What exactly is the problem you are having? Can you post a small > > detailed > > example? > > > > As I understand your proposal you want to deploy from the outside in > > rather > > than the inside out. I think this won't work for most packages: for > > instance I don't think we can put our sar packages inside ejb-jars so > > they > > could get deployed after the ejb-jar, whereas you can put an ejb-jar > > inside > > a sar to get it deployed before the sar. > > > > Please explain further. > > > > david jencks > > > > On 2002.03.18 04:19:56 -0500 Vesco Claudio wrote: > > > Hi alls! > > > > > > I think we have a little bug in MainDeployer. > > > > > > I'll try to explain the problem in my bad English :-( > > > > > > When I deploy & redeploy an ear I have an JSR-77 exception > > > (javax.management.InstanceNotFound) because: > > > > > > deploy > > > init > > > init current deployer invoked > > > init subdeployers invoked > > > > > > create > > > create subdeployers invoked > > > create current deployer invoked > > > > > > start > > > start subdeployers invoked > > > start current deployer invoked > > > > > > undeploy > > > stop > > > stop current deployer invoked > > > stop subdeployers invoked > > > > > > destroy > > > destroy current deployer invoked > > > destroy subdeployers invoked > > > > > > I think the right order is: > > > > > > deploy > > > init (ok) > > > init current > > > init subdeployers > > > > > > create > > > create current > > > create subdeployers > > > > > > start > > > start current > > > start subdeployers > > > > > > undeploy > > > stop > > > stop subdeployers > > > stop current > > > > > > destroy > > > destroy subdeployers > > > destroy current > > > > > > > > > When I have modified the MainDeployer with this new order the > > exception > > > has not been take place. > > > > > > If Marc is of agreement can apply the patch or I can post it. > > > > > > Claudio > > > > > > > > > _______________________________________________ > > > Jboss-development mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
