[jboss-dev-forums] [Design of POJO Server] - Re: JBAS-1841 - ServiceController/Microcontainer integration

[scott.stark@jboss.org]

I made good progress on tieing these together today. The server bootstrap is looking like:


  | <!-- A ProfileServiceBootstrap bootstrap descriptor that uses the simple
  | VFSDeploymentScanner that goes directly to the MainDeployer rather than the ProfileService.
  | $Id$
  | -->
  | <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |    xsi:schemaLocation="urn:jboss:bean-deployer:2.0 bean-deployer_2_0.xsd"
  |    xmlns="urn:jboss:bean-deployer:2.0">
  |    <!-- -->
  |    <bean name="ProfileService" class="org.jboss.system.server.profileservice.ProfileServiceImpl">
  |       <constructor>
  |          <parameter>${jboss.server.name}</parameter>
  |       </constructor>
  |       <property name="profileRoot">${jboss.server.home.url}/profile</property>
  |    </bean>
  | 
  |    <!-- The MainDeployer -->
  |    <bean name="MainDeployer" class="org.jboss.deployers.plugins.MainDeployerImpl">
  |       <property name="VFSFactory"><inject bean="VFSFactory"/></property>
  |    </bean>
  |    <!-- The factory for VFS instances -->
  |    <bean name="VFSFactory" class="org.jboss.vfs.file.DefaultVFSFactory">
  |    </bean>
  | 
  |    <!-- Deployers. Declaration order defines the deployer chain order
  |    -->
  |    <bean name="ClassLoadingDeployer" class="org.jboss.deployers.plugins.classloading.ClassLoadingDeployer">
  |       <property name="mainDeployer"><inject bean="MainDeployer"/></property>
  |    </bean>
  |    <bean name="BeanDeployer" class="org.jboss.deployers.plugins.bean.BeanDeployer">
  |       <property name="mainDeployer"><inject bean="MainDeployer"/></property>
  |    </bean>
  |    <bean name="SARDeployer" class="org.jboss.deployment.SARDeployer">
  |       <property name="useNamespaceAwareParser">true</property>
  |    </bean>
  | 
  |    <!-- A bean that setups a jboss-4.0.x type of jmx kernel to support the
  |       the legacy mbean deployments handled by the SARDeployer
  |    -->
  |    <bean name="JMXKernel" class="org.jboss.system.server.jmx.JMXKernel">
  |       <property name="serverImpl"><inject bean="ProfileService"/></property>
  |       <property name="serviceController"><inject bean="SARDeployer" property="serviceController" /></property>
  |    </bean>
  | 
  |    <!-- Hot deployment service that directly uses the MainDeployer -->
  |    <bean name="VFSDeploymentScanner" class="org.jboss.deployers.plugins.scanner.VFSDeploymentScannerImpl">
  |       <property name="mainDeployer"><inject bean="MainDeployer"/></property>
  |       <property name="VFSFactory"><inject bean="MainDeployer" property="VFSFactory" /></property>
  |       <property name="URIList">
  |          <list elementClass="java.net.URI"><value>${jboss.server.home.url}/deploy/</value></list>
  |       </property>
  |       <property name="scanPeriod"><value>5000</value></property>
  |    </bean>
  |    
  | </deployment>
  | 

The JMXKernel is a stripped down version of the jboss-4.0.x ServerImpl that sets up the jmx env needed by the SARDeployer/ServiceController. Still haven't actually gotten an mbean service to deploy, but getting close.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963092#3963092

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963092