John, The empty namespace on the child element of the SOAP Body is caused by the fact that the WSDL specifies "rpc" style in the <soap:binding> definition, but it doesn't specify a namespace attribute in the <soap:body> definitions. (When using RPC style, you must specify a namespace attribute in <soap:body>.)
I'm really astonished to see a .NET server exposing a WSDL that uses RPC/Literal -- .NET doesn't support RPC/Literal. This WSDL is totally wrong for an RPC style service. It looks like a wrapped document/literal style service. As I said in another response I made to you yesterday, you should change the style to "document", and then it should work. (As I mentioned yesterday, you do have a number of elements defined in the schema with no types defined -- you should also define their types.) Anne On 7/14/05, John Baker <[EMAIL PROTECTED]> wrote: > Hello, > > I am using Axis (1.2.1) to connect to a .NET server, but the server isn't > deserialising the Axis generated message correctly. > > I've used this wsdl: > http://www.javasystemsolutions.com/serviceRequestConnector.wsdl > > And I've used the wsdl2java program to create my Java stubs. > > Now this is what Axis generates for the SubmitGeneralServiceRequest method: > > <?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> > <SubmitGeneralServiceRequest xmlns=""> > <ns1:SubmittedGeneralServiceRequest > xmlns:ns1="http://www.caps-solutions.co.uk/schema/uniform/72b/servicerequest/sr/srtypes";> > <ns1:ServiceRequestIdentification > > (etc.) > > The .NET server replies: > > Server was unable to process request. A valid > SubmittedGeneralServiceRequestType object is required > > Now it strikes me that xmlns="" looks wrong. > > Does anyone have any ideas what's going on? > > Thanks, > > > John >
