What is the use case for this type of depends? Right now we still have several bugs relating to dependency and deployment issues that I want stablized before we continue to expand the notion of the service life-cycle.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, July 27, 2002 1:26 PM Subject: Re: [JBoss-dev] Re: [jboss-cvs] jboss-system/src/main/org/jboss/deployment ClasspathExtension.java > 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 > ------------------------------------------------------- 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
