Hya Peter thanks for the quick response :-)
1) Vista 64bit, Tomcat 6.0.14, Security Manager not enabled, default local tomcat install for intial testing. Java Platform JDK 1.6. Netbeans 6.7 used for development and deployment. 2) Yep that's spot on - the services are hostet elsewhere (.net based) and are already being used with other clients. In the end the client will have to be deployed on a tomcat 6 server (not sure about the exact revision yet). Glassfish and the local tomcat install are just used for initial testing. - Raphael -----Ursprüngliche Nachricht----- Von: peter.crowth...@googlemail.com [mailto:peter.crowth...@googlemail.com] Im Auftrag von Peter Crowther Gesendet: Montag, 17. August 2009 11:31 An: Tomcat Users List Betreff: Re: Problem with SOAP Response Raphael, could we just check a few things? 1) OS, Tomcat version, Java version? Is the security manager enabled? What (if any) of the default options have been changed on the Tomcat installation? 2) I think I read the following into your question: Your Web services are hosted somewhere else. They're not on Tomcat, not in Glassfish, do not change, and are not part of the problem. However, you're calling them from a servlet hosted in Glassfish or Tomcat. When the servlet is hosted in Glassfish, the calls work. When the servlet is hosted in Tomcat, the calls do not work. Have I got this right? If not, what is the real situation? - Peter 2009/8/17 Raphael Hürzeler <huerze...@netvision.ch> > Hya everyone, > > I'm pretty new to Tomcat and after much googling didn't yield anything that > helped me I'm trying my luck here ;-) > > > > My current problem is that I'm trying to access a Webservice (via wsdl, > classes are generated in netbeans, one custom binding was needed to resolve > a naming conflict in a response object) > > > > Headers are also modified to allow for 2 custom fields to be transmitted on > the request (the response doesn't contain these and we don't need them > either). > > > > The Request is being sent and the response is received on my end (checked > with Wireshark). > > Tomcat seems to have a problem interpreting this response though: > > > > Exception: javax.xml.ws.soap.SOAPFaultException: MustUnderstand > headers:[{http://www.w3.org/2005/08/addressing}Action<http://www.w3.org/2005 /08/addressing%7DAction>] > are not understood > > > > I've done initial testing with glassfish and there everything works > perfectly. > > > > One difference I've also noticed between glassfish and tomcat is that on > tomcat some of the basic headers aren't being generated in the request (To > and Action), I've modified the headers accordingly to send these out (exact > copies of what glassfish generates automatically) > > > > Any thoughts or ideas on how to resolve this would be much appreciated. > > > > cheers, > > Raphael > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
