"scott.stark(a)jboss.org" wrote :
|
| | <!-- The ManagedObjectFactory -->
| | <bean name="ManagedObjectFactory">
| | <constructor
factoryClass="org.jboss.managed.api.factory.ManagedObjectFactory"
factoryMethod="getInstance"/>
| | </bean>
| | ...
| | <!-- POJO Deployment -->
| | <bean name="BeanMetaDataICF"
class="org.jboss.deployers.plugins.managed.BeanMetaDataICF">
| | <install bean="ManagedObjectFactory"
method="setInstanceClassFactory">
| | <parameter>
| | <value>org.jboss.beans.metadata.spi.BeanMetaData</value>
| | </parameter>
| | <parameter>
| | <this />
| | </parameter>
| | </install>
| | <uninstall bean="ManagedObjectFactory"
method="setInstanceClassFactory">
| | <parameter>
| | <value>org.jboss.beans.metadata.spi.BeanMetaData</value>
| | </parameter>
| | <parameter>
| | <null />
| | </parameter>
| | </uninstall>
| | <property name="controller"><inject
bean="jboss.kernel:service=KernelController"/></property>
| | </bean>
| | ...
| | <!-- JMX Deployment -->
| | <bean name="ServiceMetaDataICF"
class="org.jboss.system.deployers.managed.ServiceMetaDataICF">
| | <property name="mbeanServer"><inject
bean="JMXKernel" property="mbeanServer"/></property>
| | <install bean="ManagedObjectFactory"
method="setInstanceClassFactory">
| | <parameter>
| | <value>org.jboss.system.metadata.ServiceMetaData</value>
| | </parameter>
| | <parameter>
| | <this />
| | </parameter>
| | </install>
| | <uninstall bean="ManagedObjectFactory"
method="setInstanceClassFactory">
| | <parameter>
| | <value>org.jboss.system.metadata.ServiceMetaData</value>
| | </parameter>
| | <parameter>
| | <null />
| | </parameter>
| | </uninstall>
| | </bean>
| |
|
You could perhaps change that type to which ICF is mapped against
is contract of ICF:
| public interface ICF<T>
| {
| Class<T> getType();
| }
|
then you could use callback mechanism on ManagedObjectFactory,
reducing this installs xml. ;-)
"scott.stark(a)jboss.org" wrote :
| I would like to break the ManagedObjectCreator into a separate
DeploymentStage.INSTALLED deployer that has the ManagedObjectFactory injected into it.
|
| Any objections?
|
Meaning you would remove current man+deployers code
and create new deployer - at INSTALLED stage?
"scott.stark(a)jboss.org" wrote :
| Is this the last change to cut the JBDEPLOY-2.0.0.GA, or is a JBDEPLOY-2.0.0.CR4
needed?
|
I'll probably cut new MC and Deployers release.
To at least test current changes for a few days in AS.
Let me know when you're done with your changes.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185446#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...