JBossDeveloper

Rather than the MC which just has a more direct "DO THIS" style metadata.

One way to do the strong integration without having a higher level abstraction
would be to have the classloaders become http://anoncvs.forge.jboss.com/viewrep/~raw,r=1.3/JBoss/microkernel/src/main/org/jboss/kernel/spi/dependency/KernelControllerContextAware.java

That way as new classloaders are injected into the repository the repository could
choose to restart some classloaders with new configuration and hence their
related deployments.
Using the controller context it has been passed.

<bean name="WARDeployment">
 <classloader><inject bean="WARCL"/>
</bean>

<bean name="WARCL">
 <install bean="EAR-CL-RESPOSITORY"/>
</bean>

<bean name="EJBDeployment">
 <classloader><inject bean="EJBCL"/>
</bean>

<bean name="EJBCL">
 <install bean="EAR-CL-RESPOSITORY"/>
</bean>

Update: I've reworked the tests to also include the xml classloader definition.
The schema needs fixing see the FIXME in the xsd and also we need to do the beanfactory.

"adrian@jboss.org" wrote:

Ok. But the current kernel tests don't really have a "deployment". The xml versions of
the test do.
These should probably be brought inline with the programmatic versions using
an AbstractKernelDeployment rather than deploying beans individually.

AbstractKernelDependencyTest
 protected ControllerContext install(int number, String name) throws Throwable
 {
 if (xmltest)
 {
 deploy(number);
 return util.getContext(name);
 }
 else
 {
 return util.install(beanMetaDatas[number]);
 }
 }

I can look at fixing this if you like?

Yes, that would be good as this discrepency is why I simply did not get into changing the KernelDeployment.

Update: I've done the deployment level classloader

<?xml version="1.0" encoding="UTF-8"?>

<deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:jboss:bean-deployer bean-deployer_1_0.xsd"
 xmlns="urn:jboss:bean-deployer">

 <bean name="URL" class="java.net.URL">
 <constructor factoryClass="org.jboss.test.classloading.vfs.ClassLoaderUtil"
 factoryMethod="getLocation">
 <parameter>org.jboss.test.kernel.deployment.test.DeploymentClassLoaderTestCase</parameter>
 </constructor>
 </bean>

 <bean name="DeploymentClassLoader" class="org.jboss.test.classloading.vfs.VFSClassLoader">
 <constructor factoryClass="org.jboss.test.classloading.vfs.VFSClassLoaderFactory"
 factoryMethod="newClassLoader">
 <parameter><array><inject bean="URL"/></array></parameter>
 </constructor>
 </bean>

 <bean name="BeanClassLoader" class="org.jboss.test.classloading.vfs.VFSClassLoader">
 <constructor factoryClass="org.jboss.test.classloading.vfs.VFSClassLoaderFactory"
 factoryMethod="newClassLoader">
 <parameter><array><inject bean="URL"/></array></parameter>
 </constructor>
 </bean>

</deployment>

<?xml version="1.0" encoding="UTF-8"?>

<deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:jboss:bean-deployer bean-deployer_1_0.xsd"
 xmlns="urn:jboss:bean-deployer">

 <classloader><inject bean="DeploymentClassLoader"/></classloader>

 <!-- USES THE CLASSLOADER FROM THIS DEPLOYMENT -->

 <bean name="DeploymentConfiguredClassLoader" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl">
 <property name="string">String1</property>
 </bean>

 <!-- USES A SPECIFIC CLASSLOADER -->

 <bean name="BeanConfiguredClassLoader" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl">
 <classloader><inject bean="BeanClassLoader"/></classloader>
 <property name="string">String1</property>
 </bean>

 <!-- USES THE DEPLOYER'S TCL -->

 <bean name="NotConfiguredClassLoader" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl">
 <classloader><null/></classloader>
 <property name="string">String1</property>
 </bean>

</deployment>

You obviously don't need to set the classloader to null if you haven't configured
a deployment level classloader.

Still to do.

* Tidyup the xml and SchemaBinding such that only reasonable ValueMetaData can be
inserted into the ClassLoaderMetaData
* Add ClassLoaderMetaData to the beanfactory.

"adrian@jboss.org" wrote:
Still to do.

* Tidyup the xml and SchemaBinding such that only reasonable ValueMetaData can be
inserted into the ClassLoaderMetaData
* Add ClassLoaderMetaData to the beanfactory.

 /**
 * Get the class info for the element type
 *
 * todo FIXME classloader
 * @return the class info
 * @throws Throwable for any error
 */
 protected ClassInfo getElementClassInfo() throws Throwable
 {
 if (elementType == null)
 return null;

 return configurator.getClassInfo(elementType, Thread.currentThread().getContextClassLoader());
 }

This work didn't have a JIRA task:
http://jira.jboss.com/jira/browse/JBMICROCONT-58