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
