On 2001.11.30 13:11:43 -0500 David Budworth wrote: > First off, thanks David J. for adding the test case.
glad you caught the problem. > > Anyway, > > For my own project, I have made a base Dynamic MBean for my own code > that all my MBeans are based on. > > Mainly to avoid the whole MyClass.java must have a MyClassMBean.java > type thing that really doesn't work for me given what I use my custom > mbeans for. > > And to allow the subclasses to define their own descriptions of > methods/params etc.. > > I added to my base class start() and stop(), which JBoss sees and does > indeed call. > > I don't (yet) however, define Name, State, StateString attributes that > are in ServiceMBean. > > Just start() and stop() > > Does JBoss make use of the ServiceMBean attributes? Or are they just > for informational purposes? The only use is for ServiceMBean to tell you not to call start twice in a row etc. It's useful for people to see if their mbean started successfully also;-) david jencks > > And, are start()/stop() JBoss-isms? Or some kind of standard thing? I > couldn't find them in the JMX spec. > > Would I magically get better managability by making my dynamic base > implement ServiceMBean, and make them work like ServiceMBeanSupport? The init and destroy are not used in mbeans any more. Rickard keeps claiming they are a good idea, but I don't see why yet. He wants init to only set up the mbean from its attributes, not using external references, but there is no way to enforce this, and as far as I can tell all you would gain is a little speed from not doing all the setup work in start. I do think a different division of responsibility for persistence is a good idea. david jencks > > -David > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
