From: David J. <dav...@di...> - 2002-07-31 01:45:45
|
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 On 2002.07.30 19:58:37 -0400 Scott M Stark wrote: > How is that, a bug? > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > ----- Original Message ----- > From: "Michael Stanley" <mst...@mi...> > To: <jbo...@li...> > Sent: Tuesday, July 30, 2002 3:25 PM > Subject: Re: [JBoss-user] MBean interfaces to EJBs > > > > > Then override the name in preRegister. Having to specify a name > > > in the mbean service descriptor does not prevent this does it? > > > > Yup. > > > > > ------------------------------------------------------- > 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 > JBo...@li... > https://lists.sourceforge.net/lists/listinfo/jboss-user > > |