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</interceptor>
<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.EntitySynchronizationInterceptor</interce
ptor>
<interceptor>org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor</interce
ptor>
</interceptor>
<default-attribute
name="instance-cache">org.jboss.ejb.plugins.EntityInstanceCache</default-att
ribute>
...
...
...
</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
