Qualified Namespace Issue

[AliasMrJones]

We're trying to get IBM Websphere Business Integration to talk to a .net
webservice. We're using document/literal. WBI is sending a soap request
that looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XML Spy v4.4 U (http://www.xmlspy.com) by Eric Moore
(Scholastic, Inc.) -->
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<ns0:individualName xmlns:ns0="IndivName_Service">
<ELEMENT 1>
<ELEMENT2 ATTRIBUT1="X" ATTRIBUTE2="Y">
<ELEMENT3>VALUE</ELEMENT3>
</ELEMENT2>
</ELEMENT 1>
</ns0:individualName>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The ns0: being on the root, but not on all the rest of the elements is
causing .net to get a null object. If the ns0: is removed from the soap
message, everything works. If ns0: is added to every element, it works as
well. Is the above structure valid and/or is there some known issue with the
above structure?

Thanks,

Eric

[Stan Kitsis [MSFT]]

Hi Eric,

You need to specify where ELEMENT1, ELEMENT2, and ELEMENT3 are coming from.
Adding xmlns="IndivName_Service" should also fix the problem:

<ns0:individualName xmlns:ns0="IndivName_Service" xmlns="IndivName_Service">

or

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="IndivName_Service">

--
Stan Kitsis
Program Manager, XML Technologies
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"AliasMrJones" <Al**********@discussions.microsoft.com> wrote in message
news:EB**********************************@microsof t.com...

We're trying to get IBM Websphere Business Integration to talk to a .net
webservice. We're using document/literal. WBI is sending a soap request
that looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XML Spy v4.4 U (http://www.xmlspy.com) by Eric Moore
(Scholastic, Inc.) -->
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<ns0:individualName xmlns:ns0="IndivName_Service">
<ELEMENT 1>
<ELEMENT2 ATTRIBUT1="X" ATTRIBUTE2="Y">
<ELEMENT3>VALUE</ELEMENT3>
</ELEMENT2>
</ELEMENT 1>
</ns0:individualName>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The ns0: being on the root, but not on all the rest of the elements is
causing .net to get a null object. If the ns0: is removed from the soap
message, everything works. If ns0: is added to every element, it works as
well. Is the above structure valid and/or is there some known issue with
the
above structure?

Thanks,

Eric