> -----Original Message----- > From: Simon Nash [mailto:[email protected]] > Sent: Monday, November 21, 2011 7:49 PM > To: [email protected] > Subject: Re: Wrong result type in web service operation > > Scott Kurz wrote: > > Sebastian, > > > > Do you have a tool to show you the SOAP request being sent over the > wire? > > > > I don't think we have a lot of Tuscany logging in place, but Axis2 > has > > some logging that could be enabled if we had to. > > > > Scott > > > TCPMon is a convenient way of doing this if you're able to change the > sending or receiving port number. If not, you could use Wireshark > which is an excellent tool. > > Simon
Thanks for the pointer to TCPMon. I routed two requests through localhost:9090. The good request is from the wrapped style interaction. The bad one is from the bare style interaction which is the subject of this conversation. The bad request has a non-empty SOAP action and is missing the namespace for the operation in the SOAP body. The latter difference is clearly significant, as pasting this SOAP-XML into a client like SOAP-UI will produce the same fault that I am seeing in Tuscany. BTW, The Axis2 logging can be enabled by placing a log4j.properties file on the classpath, but the logging output is not very helpful, as it mainly traces processing steps without showing the attendant data. -- Sebastian IDS Scheer Consulting GmbH Geschäftsführer/Managing Directors: Kamyar Niroumand, Ivo Totev Sitz/Registered office: Altenkesseler Straße 17, 66115 Saarbrücken, Germany - Registergericht/Commercial register: Saarbrücken HRB 19681 http://www.softwareag.com
