I have run the testsuite.
I have confronted the result with
http://www.lubega.com/testarchive/reports-20020318-0547/
I have errors in org.jboss.test.jmx.test, = lubega.
I have *no* errors in org.jboss.test.management.test, = lubega
I have errors in org.jboss.test.readahead.test.ReadAheadUnitTestCase !=
lubega
entity already found
remainder = lubega :-)
I think is better to create/start an outer container before an inner
container -> an inner container *is* contained in the outer container. I
think this is not only better for jsr 77 but better for
deploying/classloading etc etc etc, but I don't know everything in jboss
:-)))
Claudio
> -----Original Message-----
> From: David Jencks [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, March 18, 2002 6:05 PM
> To: Vesco Claudio
> Cc: Jboss Dev
> Subject: Re: [JBoss-dev] Ordering part 2 :-)
>
> On 2002.03.18 11:46:32 -0500 Vesco Claudio wrote:
> > It does not stop deploy/redeploy, only produce an exception in log.
> >
> > I test the testsuite now :-)
>
> Thanks
> >
> > Per quanto riguarda la discussione che avvenuta a riguardi
> > dell'ordinamento, penso che le dipendenze tra risorse debbano essere
> > indicate in un jboss-application.xml
> >
> > Concerning the recently discussion, I think that the dependecies
> between
> > resources must be included in application-jboss.xml.
> >
> > The order proposed in MainDeployer I think is this correct KISS :-)
> I think there are arguments in favor of both orders.
> >
> > If I have a ear containing sar containing ear etc etc etc, it does
> not
> > standard (j2ee compliant) and so -> application-jboss.xml :-)
>
> True, but some nesting is allowed by j2ee, and needs to be handled
> without
> any jboss-application.xml needed.
>
> I think that most of these problems will go away when we can represent
> most
> dependencies as (automatically generated) mbean dependencies. I think
> we
> will be able to deploy just about anything packaged in just about any
> nesting without needing explicit deployment instructions.
>
> btw, I think two possible fixes I would be happier with are
>
> 1. jsr 77 mbeans destroy all their children when they are destroyed.
>
> 2. create, and start steps remain ordered from inside to outside, stop
> step
> remains ordered from outside to inside, destroy step is reversed to
> from
> inside to outside.
>
> Thanks
> david jencks
> >
> > Claudio
> >
> > > -----Original Message-----
> > > From: David Jencks [SMTP:[EMAIL PROTECTED]]
> > > Sent: Monday, March 18, 2002 5:22 PM
> > > To: Vesco Claudio
> > > Subject: Re: [JBoss-dev] Ordering part 2 :-)
> > >
> > > Does this actually stop undeployment/redeployment or only produce
> an
> > > ugly
> > > log? Previously Andy indicated (I think) that the jsr-77 stuff
> should
> > > not
> > > impede redeployment, no matter how many errors it put in the log.
> > >
> > > I am _very_ worried about reversing the order of subdeployment
> nesting
> > > without a more complete dependency mechanism. If this is not
> stopping
> > > redeployment I would prefer to leave it till I can think about it
> more
> > > carefully. Have you seen what happens with your change with
> > > 1. the testsuite
> > > and
> > > 2. more complicated packaging such as ear containing sar
> containing
> > > ear
> > > containing rar?
> > >
> > > Thanks
> > > david jencks
> > >
> > > On 2002.03.18 09:48:08 -0500 Vesco Claudio wrote:
> > > > Only for you :-)
> > > >
> > > > I have deployed bench.ear from testsuite and when I undeploy it
> I
> > > have
> > > > this exception, ehm zipped :-)
> > > >
> > > > With call reordering I don't have exception :-)
> > > >
> > > > Claudio
> > > >
> > > >
> > > > <<undeploy-exception.zip>> <<Patch.zip>>
> > > >
> > > > > -----Original Message-----
> > > > > From: Vesco Claudio [SMTP:[EMAIL PROTECTED]]
> > > > > Sent: Monday, March 18, 2002 3:27 PM
> > > > > To: 'David Jencks'; [EMAIL PROTECTED]
> > > > > Subject: RE: [JBoss-dev] Ordering part 2 :-)
> > > > >
> > > > > I'll retest jboss without my patchs :-)
> > > > >
> > > > > please wait a moment :-)
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: David Jencks
> [SMTP:[EMAIL PROTECTED]]
> > > > > > Sent: Monday, March 18, 2002 3:24 PM
> > > > > > To: [EMAIL PROTECTED]
> > > > > > Subject: Re: [JBoss-dev] Ordering part 2 :-)
> > > > > >
> > > > > > 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
> > > > >
> > > > > _______________________________________________
> > > > > 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
