[jboss-dev-forums] [Design of POJO Server] - Re: Removing ClassLoading from jboss-bootstrap

[wolfc]

"adrian at jboss.org" wrote : The basic idea is to have a pluggable bootstrap. The bootstrap.start() should run
  | under its own classloader as TCL not the classpath otherwise all sort of side effects
  | break (e.g. loading property editors, and other dynamic classloading, etc.).
I still don't see how this can happen?
The app classloader contains virtually nothing.
"adrian at jboss.org" wrote : In JBoss the bootstrap is two stage (actually it is multiple).
  | 
  | 1) To load the bootstrap implementation itself (the mc + profile service)
Profile Service isn't in scope yet. We're at rock bottom, stage #1, a bootstrapping framework with which Reloaded can bootstrap Profile Service itself.
"adrian at jboss.org" wrote : 
  | 2) To load the bootstrap xmls
  | 
  | As long as the called code doesn't have to worry about setting the TCL itself
  | (error prone and it is not likely to know what the correct CL is) 
  | I don't have a problem.
I think I'm getting it: Bootstrap should execute the following 'psuedo' descriptor:
<deployment>
  |    <classloader>preboot-cl</classloader>
  |    <bean class="org.jboss.bootstrap.MCServerImpl"/>
  |    <bean class="org.jboss.bootstrap.BootstrapDeployer"/>
  |    <classloader name="preboot-cl">
  |       bits and pieces specified by the launcher
  |    </classloader>
  | </deployment>


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

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