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. Can anyone weigh in on: * Removal of NoAnnotationCL - a URLCL which is commented to be used in RMI. Is this still the case? * AbstractServerImpl.start() to use the TCCL. Currently it's using 2 different CLs (one for starting the ServerImpl, one for the bootstraps). With no objections I'll plug ahead, test, and patch AS to match. S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223119#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...