Hi Jason,
comments below: On Thu, 3 Jan 2002, Jason Dillon wrote: > > > I don't think that the actual component has any business providing > the > > > name which it will be bound under, rather the code which registers > it > > > should decide that. > > > > Aren't the hard-coded names for the mbean itself only used if no name > is > > provided when the mbean is created? Does the spec require such names? > I'd > > be pretty happy just putting them in as a comment/suggestion if they > > aren't > > spec-required. > > That was probably the initial design, but there are lots of places in > Jboss where we simply ignore the supplies/configured object name and > just return the default. > > I have been changing this everywhere I find, but it is still a problem. > Sorry but I've purged the CVS update notifications so I don't know which bits of code you've been changing - which is why my question may be off the mark. Are you talking about MBeans which implement MBeanRegistration and return a new ObjectName in preRegister()? If so, that returned ObjectName is *only* used if the one supplied in the preRegister() arglist is null. In this instance if the MBean doesn't return a valid ObjectName then a RegistrationException will get thrown and postRegister(false) is called on the MBean. Depending on how you are changing things (and what may have already been there) you may need to review your changes to see if you need to do any cleanup in response to a postRegister(false). Regards, Trevor _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
