XMBeans are ModelMBeans with an xml descriptor. You take a POJO and write some xml that says at least what constructors, operations, attributes, and notifications are managed. You (can) give a lot more detail about persistence policy, importance, description, etc etc (described in jmx spec) and basically add whatever else you need (interceptor stack, and as we just realized default mbean dependencies). The mbean server then sets up your object as an mbean using this info -- no standard mbean interface or dynamic mbean invoker crap needed.
Juha's book does talk about it some. I extended the implementation slightly and wrote a xdoclet task to generate the descriptor from @jmx:blahblah markup. When I wrote it the model mbean support wasn't very good in jbossmx and I haven't had time to go back and see how it is working now. I think we should move all our mbeans to xmbean very soon however -- immediately post 3.0 I hope. david jencks On 2002.04.21 02:51:34 -0400 Bill Burke wrote: > So, xmbeans are what I'm suggesting? What are xmbeans? Are they talked > about in Juha's book? > > Thanks, > > Bill > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of > David > > Jencks > > Sent: Sunday, April 21, 2002 2:43 AM > > To: Bill Burke > > Cc: Jboss-Dev > > Subject: Re: [JBoss-dev] RE: next-gen mbean config > > > > > > I think both of these fit well into the xmbean configuration, > > although they > > aren't there now. > > > > Earlier today I thought about putting default mbean dependencies there > -- > > such as on the naming service or tm which you might not want to repeat > in > > every mbean needing them. similar idea. > > > > david jencks > > > > On 2002.04.21 02:19:50 -0400 Bill Burke wrote: > > > Another thing we could use mbean-templates for is to define > > default mbean > > > dependencies for EJBs as well. > > > > > > > -----Original Message----- > > > > From: Bill Burke [mailto:[EMAIL PROTECTED]] > > > > Sent: Sunday, April 21, 2002 2:16 AM > > > > To: Jboss-Dev > > > > Subject: next-gen mbean config > > > > > > > > > > > > Jason got me thinking, > > > > > > > > We need a standard way of configuring some sort of MBean > > > > templates. In the future, we need to be able to define what an > > > > MBean looks like in standard meta-data that can be used as a > > > > factory to create new mbeans. We should and will be able to > > > > define distributed object frameworks like EJB, SOAP, CORBA, > > > > etc... within these templates. > > > > > > > > <mbean-template code="org.jboss.ejb.EntityContainer" > > > > name="jboss.ejb:service=EntityContainer"> > > > > <interceptors> > > > > <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> > > > > > > > > <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor> > > > > > > > > <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> > > > > <interceptor > > > > metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</in > > > > terceptor> > > > > > > > > > > <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor> > > > > > > > > <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor> > > > > > > > > > > <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor> > > > > > > > > <interceptor>org.jboss.ejb.plugins.EntitySynchronizationIntercepto > > > > r</interceptor> > > > > > > > > <interceptor>org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationIntercepto > > > > r</interceptor> > > > > </interceptor> > > > > <default-attribute > > > > name="instance-cache">org.jboss.ejb.plugins.EntityInstanceCache</d > > > > efault-attribute> > > > > ... > > > > ... > > > > ... > > > > </interceptors> > > > > </mbean-template> > > > > > > > > > > > > What about the ability to hot-deploy and hot-configure > > > > distributed object frameworks? > > > > > > > > > > > > So, if you have a tempalte-service.xml file for EJB and redeploy > > > > it, all jars get redeployed and use the default configurations > > > > defined in the mbean-template. > > > > > > > > Just some ideas, > > > > > > > > Bill > > > > > > > > > > > > > _______________________________________________ > > > 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 > > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
