Yes, depends has to be an ObjectName and it cannot have a pattern. The point of notification is one of many in the life cycle and is all that has been needed so far. Additional notifications could be added so that you could wait for the right state.
ObjectNames are fixed at registration/creation time. If you need an mbean that is so dynamic that its name is not known until it is to be registered use an mbean factory that manages the dependency issues and when approriate registers the mbean with the desired name. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Michael Stanley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 30, 2002 11:40 AM Subject: Re: [JBoss-user] MBean interfaces to EJBs > Cool. Thanks I have things working now. Very nice. > > Question on the depends: Does the value of the <depend> element have to > be the ObjectName? And if so can it be a pattern, or does it have to be > the full name? > > for example - is something like this legal -> > > <depends>*:EJBModule=MyEJB.jar,*</depends> > > Thanks again for your help, > Mike > > PS. Is my note about the sequence of the Deployment notification > accurate? If not, what is the reasoning behind the current order of > events? ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
