Looks like your right about that: If the MBean developer chooses to implement the MBeanRegistration interface, the following methods must be provided: + preRegister - This is a callback method that the MBean server will invoke before registering the MBean. The MBean will not be registered if any exception is raised by this method. This method may throw the MBeanRegistrationException which will be re-thrown as is by the MBean server. Any other exception will be caught by the MBean server, encapsulated in an MBeanRegistrationException and re-thrown. This method may be used to: + Allow an MBean to keep a reference on its MBean server. + Perform any initialization that needs to be done before the MBean is exposed to management operations. + Perform semantic checking on the object name, and possibly provide a name if the object was created without a name. ...
I don't think the issue was avoiding the generation of the service description, rather it was delaying the choice of the name which really is a rather arbitrary setting aside from its use in dependencies. The service descriptor can be generated dynamically as is done by the XSL based deployer you wrote so end of story. An mbean has to have a name. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 30, 2002 6:43 PM Subject: Re: [JBoss-user] MBean interfaces to EJBs > I think the spec indicates that if you supply an object name when you > create the mbean, that oejbct name overrides anything supplied by > preRegister. So to make the preRegister ever do anything with names for > mbeans from -service.xml files, we'd have to allow the -service.xml file to > not specify the object name. I think this wouldn't be too hard of a change. > > Maybe you could include the info needed to construct an appropriate name in > constructor arguments, which are surely present before preRegister is > called;-), and are also settable in the -service.xml. I don't see yet how > this would remove the need to generate a service.xml file or at least mbean > config for each mbean. You can always use ant filtering to replace a token > with the domain you want (and, I think, use ant property syntax inside > xdoclet tags) > > david jencks > ------------------------------------------------------- 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
