XML Namespace in WebService Request/Response

Question

Hi all,
I have a question regarding xml namespace usage in wsdl and the corresponding request/response messages.
I have already browsed quite some articles about xml namespaces as well as some forum threads, but I am still not sure.
I have the following part of a wsdl document (generated by Integration Directory), defining a targetnamespace.
u2026
<wsdl:types>
    <xsd:schema targetNamespace="http://www.dorma.com/sap/xi/finance"
                         xmlns="http://www.dorma.com/sap/xi/finance"
                         xmlns:xsd="http://www.w3.org/2001/XMLSchema">
        <xsd:element name="DebtorGetDetailResponse" type="Z_BAPI_DEBTOR_GETDETAIL_Response"></xsd:element>
        u2026
        <xsd:complexType name="Z_BAPI_DEBTOR_GETDETAIL_Response">
            <xsd:sequence>
                <xsd:element name="DEBITOR_COMPANY_DETAIL" type="BAPI1007_5" minOccurs="0">
                </xsd:element> u2026
            </xsd:sequence>
        </xsd:complexType>
        u2026
    </xsd:schema>
    u2026
</wsdl:types>
u2026
In my understanding, all types defined in the schema section of a wsdl document will be in the targetnamespace, if defined.
Therefore the element DEBITOR_COMPANY_DETAIL would be in the namesapce
http://www.dorma.com/sap/xi/finance
However, the ABAP proxy generates a response message like follows,
where only the root element is in this namespace and the child elements are in the global namespace:
<?xml version="1.0" encoding="utf-8"?>
<ns1:DebtorGetDetailResponse xmlns:ns1="http://www.dorma.com/sap/xi/finance"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <DEBITOR_COMPANY_DETAIL>
        u2026
    </DEBITOR_COMPANY_DETAIL>
    u2026
</ns1:DebtorGetDetailResponse>
Do I have a wrong understand of the wsdl (xml schema) or is this an erroneous behavior?
The problem is that some 3rd-party software web service module does not accept
the response message as not complient with the respective wsdl document.
Any input is appreciated.
Thanks
Hans
Edited by: Hans-Jürgen Schwippert on Oct 1, 2008 12:02 PM

Answer 1

I have the same problem. I am trying to connect to a webservice running on IBM websphere but it doesn't accept the xml in my request. It appears to be the same namespace issue.
Did you ever find a solution for this?
Is it a valid webservice call if you omit the namespace for an element or is this a bug in the Adaptive WS implementation?
Web Dynpro web service model generated request:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Header>
<sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/">
<enableSession>true</enableSession>
</sapsess:Session>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
look between these lines -
<ns1:tamKontrolleraKontoLastAnrop xmlns:ns1="http://schemas.fora.se/modell/tam/1.0/TAM_Data">
<AnvandarNamn>30039647</AnvandarNamn>
</ns1:tamKontrolleraKontoLastAnrop>
look between these lines -
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
As you can see the tag
<AnvandarNamn>30039647</AnvandarNamn>
is missing a namespace.
It should be
<ns1:AnvandarNamn>30039647</ns1:AnvandarNamn>
Using a third part tool called Soapui i generate this request that works:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tam="http://schemas.fora.se/modell/tam/1.0/TAM_Data">
   <soapenv:Header/>
   <soapenv:Body>
      <tam:tamKontrolleraKontoLastAnrop>
         <tam:AnvandarNamn>30039647</tam:AnvandarNamn>
      </tam:tamKontrolleraKontoLastAnrop>
   </soapenv:Body>
</soapenv:Envelope>