"ALRubinger" wrote : https://jira.jboss.org/jira/browse/JBBOOT-24 | | As it stands, Bootstrap is sensitive to arbitrary JARs on the application CP (and picked up by the extension ClassLoader). This becomes especially apparent when starting up from an Embedded environment, where we may have a full dependency set on the test CP. | | AS currently sidesteps this problem by careful inclusion of classes in the run.jar. | | What I'd like to do is remove setting of the TCCL from jboss-bootstrap entirely, leaving this task up to the client (launcher). Some local tests yield much better results and allow the bootstrap to become adaptable to a wider range of runtime environments. | 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.). In JBoss the bootstrap is two stage (actually it is multiple). 1) To load the bootstrap implementation itself (the mc + profile service) 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. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223631#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...