On 2002.03.05 00:03:48 -0500 Andreas Schaefer wrote: > Hi David > > > On 2002.03.04 23:10:25 -0500 Andreas Schaefer wrote: > > > Hi Geeks > > > > > > JSR-77 spec. is still changing and therefore a > > > moving target. > > > > > > I think that JSR-77 MBeans should be converted > > > to Juha's XMBean. Because I am too lazy to write > > > the deployment descriptors I am going to use David > > > Jencks XDoclet "jbossmx" to generated the XMBean > > > DDs. > > > > > > > excellent. I'm hoping to move all the mbeans from standard mbeans to > > xmbeans when the xmbean is a little more stable. Will the jsr-77 stuff > be > > implementable as interceptors in the xmbean stack? Will you need > separate > > registrations for the "jboss" mbean view of the object and the "jsr-77" > > view? > > It seems that I missed this discussion. What do you mean with "as > interceptors > in the xmbean stack" ? >
The xmbean implementation appears to have an interceptor stack similar to the jboss ejb interceptor stack. I'm planning to use it for things like "when you change a set of attribute values, stop, change values, and restart" or "just change values" or "destroy the mbean and make a new one". I wonder if all the jsr-77 mandated behavior can be implemented as an interceptor on the managed mbean, or if you really need another separate independent object. david jencks > > > This means that the only classes provided from JSR-77 > > > are: > > > - MEJB Home and Remote Interface > > > - various Statistics and Stats > > > > > > The rest is the class being the target of the XMBean which > > > still contains the static "create" and "destroy" method. > > > > Are these static methods required by the jsr-77 stuff? I'm trying to > move > > towards "the mbean is the object". Already ejbs are mbeans (Container) > and > > ejb-modules are mbeans. In the jca rewrite I'm working on the > > ConnectionManager is an mbean providing the ConnectionFactory service: > no > > more loaders. I'm not all that familiar with these static methods, but > I > > wonder how useful they will be if everything you are managing is > already > an > > mbean. > > No these static methods are not required by JSR-77. The static methods > are > only > there to encapsulate the necessary steps to create / destroy the JSR-77 > MBean. > We could also use either a factory or add these steps to the JBoss > component. > > My idea of the JSR-77 implementation is that the JSR-77 MBeans are > separate > from the JBoss components providing that feature. This allows us to be > more > flexible because the JSR-77 component can still make some adjustments or > convertions to meet the JSR-77 requirements. > Currently JMX is still used to comuniate between JBoss and JSR-77 > components > but maybe this must be changed because of performance problems for > statistics. > > Andy > > > > _______________________________________________ > 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
