A quick look at the web deployers leads to a likely candidate
(since you're creating the endpoint from a servlet init).
| package org.jboss.web.tomcat.service.deployers;
|
| public class JBossContextConfig extends ContextConfig
| {
| public static ThreadLocal<JBossWebMetaData> metaDataLocal = new
ThreadLocal<JBossWebMetaData>();
| public static ThreadLocal<JBossWebMetaData> metaDataShared = new
ThreadLocal<JBossWebMetaData>();
|
| ...
|
I haven't determined the exact mechanism, but my guess is that
parameters of the webapp that is doing the init() are interfering with
the new deployment via this ThreadLocal.
It should be relatively easy to validate this guess, by getting your test
code to fork a thread to do the deployment.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160632#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...