I think we need an additional kind of dependency: <requires [optional-attribute-name="Something"]>some.domain:service=doIt</requires>
This prevents create from being called until the other mbean is started. The new create step creates the mbean, registers it, and calls the create method. If there are only "depends" dependencies, this step proceeds. If there are "requires" dependencies, it waits before even creating the mbean. The start method can be called at any time but does nothing until all "depends" mbeans are started. Whenever a mbean gets to "started", the lists of waiting mbeans have create (for "requires") or start (for "depends") called on them. I think DeploymentInfo should also be an mbean that participates in the dependency management, so you can use "requires" to make a package deploy completely before another starts deploying. A top level depends or requires tag can be used in *-service.xml or other jboss specific dd's to make this ordering available to all packages. Thanks david On 2002.07.27 13:19:44 -0400 Scott M Stark wrote: > And how do dependencies fit into this scheme? > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > ----- Original Message ----- > From: "David Jencks" <[EMAIL PROTECTED]> > To: "Jason Dillon" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Saturday, July 27, 2002 10:00 AM > Subject: Re: [jboss-cvs] jboss-system/src/main/org/jboss/deployment > ClasspathExtension.java > > > > Well, I am still in favor of ServiceController creating each bean, > > registering it, calling create, and calling start before going on to > the > > next one. The last time I implemented something like this I think I > > completely removed the create step. Perhaps it would be acceptable to > keep > > both create and start steps, but execute all steps before moving onto > the > > next mbean? > > > > Thanks > > > > david jencks > > > > > > On 2002.07.24 17:09:38 -0400 Jason Dillon wrote: > > > Do you think it would be easy to change the ServiceController to call > > > create() right after registration with the MBeanServer? If so I > think > > > we should do this. It will allow us to use this component as a > > > replacement for the <classpath> element, thus making the system > simpler > > > and more flexible. > > > > > > I think we should do this. Can you (or anyone else) think of any > > > reasons not to? > > > > > > --jason > > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
