"richard.opalka(a)jboss.com" wrote : "adrian(a)jboss.org" wrote :
| | If it is going in the wrong tomcat context then you've obviously not setup
your
| | JBossWebMetaData correctly.
| We call JBossWebMetaData.setContextRoot("jaxws-endpoint") for sure :(
| "adrian(a)jboss.org" wrote :
| | And like I said before. Passing the thread context classloader is almost certainly
wrong
| |
| Could you review this piece of code, please?
|
jbossas/trunk/webservices/src/main/org/jboss/wsf/container/jboss50/transport/EndpointAPIHttpTransport.java
| and provide us constructive feedback e.g. what's fundamentally wrong there?
Starting from that class I get to:
| // Get the context root for this deployment
| String contextRoot = dep.getService().getContextRoot();
|
which is lost in some interfaces.
The only way for me to figure out what is going on is to open up a debugger
(or add logging) to verify the values are as you say in that code
and if they are, figuring out where in Tomcat (or one of the deployers
that processes JBossWebMetaData) they get changed or overridden.
This is a task that you can do just as well as I can.
I hope you can see why we don't feel overly eagre to help you
when all the work is assumed to be in one direction, especially
when known of the code (jbossws, web metadata or tomcat)
is actually an issue for the deployers framework or its forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160622#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...