It's not unusual (and certainly not an error) to create a new namespace for the message when using SOAP encoding. Keep in mind that the SOAP processor constructs the encoded message using the SOAP encoding data model, hence it doesn't conform to any specific schema, so realistically, it creates its own namespace. The WSDL specified that the http://bmdcs2.janbe.jnj.com/PILOT_SOAP/message/ namespace should be used via the namespace attribute on the <soap:body> element. But the _pDiversity type is defined in a different namespace, so I'd expect it to refrence that namespace in the message (as it does). This sounds like a thorny interoperability issue. I suggest asking the question on the soapbuilders list.
Anne ----- Original Message ----- From: "Jeff Greif" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 25, 2003 11:26 AM Subject: Re: Namespace Error receiving SOAP message from AXIS > The problem *may* be in the generated wsdl. The soap:body elements in the > binding introduce a new namespace > http://bmdcs2.janbe.jnj.com/PILOT_SOAP/message/ > which is not the target namespace of the wsdl. On the other hand, the > abstract operation, message and part names are in the target namespace of > the wsdl. > > Jeff > > ----- Original Message ----- > From: Micha Op de Beeck > To: [EMAIL PROTECTED] > Sent: Tuesday, June 24, 2003 11:25 PM > Subject: Namespace Error receiving SOAP message from AXIS > > > Hello all, > > I have developed a Web service with VB6 and MS Soap Toolkit 3.0. When > I test it with XMLSpy or a VB6 Client, it works fine. > > Now one of my collaegues is trying to access it using AXIS. It fails > (Restoring data into SoapMapper _pDiversity failed). > > ... > > Is AXIS this behaviour a bug, is it a MS bug or is it just an > icompatibility of the two? And above all, how can I (if at all) change > my WSDL file so that the AXIS client does not generate the wrong SOAP > call? >
