preRegister is called immeadiately after creation of the mbean. This is well before the first JBoss mbean service life cycle event and so there is no chance the name can be based on the attributes of an mbean you depend on. I see no point to allowing JBoss mbean services to be defined without a name as you would have to hard code it or come up with an alternate externalization mechanism.
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 1:23 PM Subject: Re: [JBoss-user] MBean interfaces to EJBs > > Yes, depends has to be an ObjectName and it cannot have a pattern. > > hmm... The example I showed previosuly using the pattern, seems to be > working. > > > 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. > > But according to spec ObjectNames can be specified in the preRegister() > method of MBeanRegistration implementations. From the javadoc to that > method -> > > "Allows the MBean to perform any operations it needs before being > registered in the MBean server. If the name of the MBean is not > specified, the MBean can provide a name for its registration." > > Wouldn't this be another way to specify the ObjectName rather than > making it a mandatory attribute in the mbean element of the service.xml > config file? If ObjectName still isn't specified after running > preRegister() then you can through the error, but I think making it > mandatory in the config file isn't neccessary. > > Thoughts? > > Mike > > > > > 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 > > > -- > <Mike/> > > > > > ------------------------------------------------------- > 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 > ------------------------------------------------------- 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
