[jboss-dev-forums] [Design of POJO Server] - Re: Deployers and classloading - stumbling block

[adrian@jboss.org]

I've implemented this by splitting it up into three sections:

* bootstrap - conf/jboss-service.xml
* deployers - server/config/deployers
* deployments - server/config/deploy

To prove it works, I've also got hacky but working versions
of the RARDeployer and ConnectionFactory deployer in JCA.

So we now have datasources and (as a consequence) jbossmq working.

The biggest hack is deciding what should be the thread context
classloader for the bootstrap (like the old server loader did).

For now, I'm using the "first" bootstrap deployment's classloader
which is ok in this case because there is only one.

Of course when the deployers have their own classloaders
this will be a none issue.

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

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