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

[adrian@jboss.org]

We can't actually cutover head to the new deployers yet.
There is one key piece missing.

We don't have a mechanism to add deployers that are not
in the bootstrap classpath.

e.g. The rar deployer needs classes from jboss-jca.jar
so it cannot be instantiated from deployer-beans.xml

What I propose we do is we change the profile service
to be more like the old JBoss4 mechanism such that
it does something like:

Pseudo code:

  | // conf/jboss-service.xml - for the classpath
  | DeploymentContext ctx = main.addDeployment(profile.getBootstrapURI());
  | main.process();
  | 
  | // Run the remainder of the bootstrap under the
  | // bootstrap uri's classloader
  | Thread current = Thread.currentThread();
  | ClassLoader cl = ctx.getClassLoader();
  | ClassLoader old = current.getContextClassLoader();
  | current.setContextClassLoader(cl);
  | try
  | {
  |    main.addDeployments(profile.getDeployerURIs());
  |    main.process();
  | 
  |    // Now do the rest of the deployments
  | }
  | finally
  | {
  |    current.setContextClasLoader(old);
  | }
  | 

Where we really want to get to is hot deployment of deployers
which is an issue that I'll deal with on a different thread.

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

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