Some more related dev issues:
- http://www.jboss.org/index.html?module=bbop=viewtopict=128233start=0
- http://www.jboss.org/index.html?module=bbop=viewtopict=128560
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4123842#4123842
Reply to the post :
kevglass wrote : I've been the code you pointed to but I'm still a little
confused. The AS code only seems to honour the classpath for bootstrap
deployments. Is there some similar code that applys the context class loader
for application JARs?
|
http://jira.jboss.com/jira/browse/JBAS-4206
I've been the code you pointed to but I'm still a little confused. The AS code
only seems to honour the classpath for bootstrap deployments. Is there some
similar code that applys the context class loader for application JARs?
Kev
View the original post :
kevglass wrote :
| I've spent some time looking through the code. The class loader deployed is
creating a basic class loader and storing it in the deployment context.
However, I can't find anywhere this context class loader is actually picked up
(*the bean deployer seems to use either the
Ok, so the ProfileServiceBootstrap does the class loader assignment to the
thread - thats great, I should be able to get stuff deploying now.
I'm a bit confused though. Shouldn't the deployment framework honour the class
loader set in the context? The change I made was (probably incorrectly)
