Still searching for an answer on this one. Feedback from anyone doing message-style services would be appreciated.
My primary question is this: Is the SOAP spec responsible for the behaviour of Axis in nesting literal messages within 2 root tags? EG: <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <myMethod xmlns="http://www.myurl.com";> <myMethod xsi:type="xsd:anyType"> ...actual payload doc content here... I'm interested to know:- 1) Why are there 2 tags inserted at this level? 2) Has anyone else tested literal (message) style services with a .NET client? (It seems that a .NET client doesn't send or expect in return this double payload root tag.) 3) Do other users of message-style services see the same behaviour at both client and server end of Axis? regards Nick Ardlie. ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************
