It would work in both, but for what Bill wants, I think you are correct.
True, it would work in both, as VFSClassLoaderFactory10 extends ClassLoadingMetaData.
But it depends where you're using, and since you mostly mention / suggest the usage of jboss-classloading.xml,
it wouldn't work there unless we used <classloading>.
Although as I understand it, he is actually creating a bean inside a deployment?
Yes.
Another thing to mention with Bill worrying about the order if multiple -beans.xmls are involved.
If you declared proper dependency on this new classloader bean, the order doesn't matter.
e.g.
<bean name="foo" class="...">
<classloader><inject bean="maven:re:2.0-CR1-classloader"/><classloader>
</bean>
This bean would wait in pre PRE_INSTALL state until that classloader bean is available.
Aka it would be registered, but not yet "class info" described, since its classloader is not yet available.
Bill's approach wont know anything about the scoping rules of the deployment
as he correctly points out.
Yes, as that classloader creation skips VDF usage -- it's a plain (cl) bean.
On Wed, Jul 14, 2010 at 9:43 AM, Ales Justin
<ales.justin@gmail.com> wrote:
> <classloader name="resteasy-classloader"
> xmlns="urn:jboss:classloader:1.0" export-all="NON_EMPTY" import-all="true">
> <requirements>
> <module name="org.jboss.resteasy:resteasy-jaxrs" version="2.0-RC1">
> </requirements>
> </classloader>
The top element here should actually be <classloading>, not <classloader>.
_______________________________________________
jboss-development mailing list
jboss-development@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development