|
From: Carlos Q. <car...@ge...> - 2002-01-31 11:13:35
|
Hi >Hi, <snip> > >Ok, so it is useful only for MBeans. Yes that's the idea > >> A more refined version could do the cheking beforehand > >Well, if you use it only for MBeans, no check: use MBeanConstructorInfo=20 metadata. How can you get a MBeanConstructorInfo if your only data is classname? I was thinking to use you MBeanIntrospector class > >> > Finally, unless you perform instantiate and register in 2=20 >> http requests (I >> > guess you don't), doing createMBean or instantiate +=20 >> registerMBean is the >> > same. One call is probably simpler. >> Ok. I'm doing registerMBean, that's also better since if the=20 >> class is not=20 >> MBean it won't be instantiated, will be? > >No, it will be instantiated. Checks are done upon registration. You can=20 create whatever class with instantiate. Perhaps this is not desirable in this case. You would like the object not= to=20 be create unless it can be a MBean. This can be enforced outside the=20 registerMBean method tough > >Simon > > >_______________________________________________ >Openjmx-devel mailing list >Ope...@li... >https://lists.sourceforge.net/lists/listinfo/openjmx-devel > |