Error consuming WSDL from tool Query as Webservice for Business Objects

[Former Member]

I am running into a ABAP syntax error when trying to generate the client proxy from a WSDL that was generated by the business objects tool "Query as a Webservice".

The error is "Exception occurred in library handler. Incorrect value: Target name space must be absolute URI QssWSTest".

We were able to consume this WSDL and generate the client proxy until we applied support packs. We are now at ECC 6.0 release 7.0 level 16.

The WSDL is:

<?xml version="1.0" encoding="UTF-8" ?>

<definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="QaaWSTest" xmlns:tns1="dsws.businessobjects.com" targetNamespace="QaaWSTest" xmlns="http://schemas.xmlsoap.org/wsdl/" name="queryasaservice">

<types>

<s:schema elementFormDefault="qualified" targetNamespace="QaaWSTest">

<s:element name="runQueryAsAService">

<s:complexType>

<s:sequence>

<s:element name="login" type="s:string" />

<s:element name="password" type="s:string" />

<s:element minOccurs="0" maxOccurs="unbounded" name="Enter_value_s__for__Customer_Number_" type="s:string" />

</s:sequence>

</s:complexType>

</s:element>

<s:complexType name="Row">

<s:sequence>

<s:element name="Customer_Number" type="s:string" />

<s:element name="Material" type="s:string" />

<s:element name="Include_Exclude_Indicator" type="s:string" />

<s:element name="UsageMonth_YYYYMM" type="s:string" />

<s:element name="Usage_Hours" type="s:double" />

<s:element name="Actual_Charge" type="s:double" />

</s:sequence>

</s:complexType>

<s:complexType name="Table">

<s:sequence>

<s:element name="row" minOccurs="0" maxOccurs="unbounded" type="s0:Row" />

</s:sequence>

</s:complexType>

<s:element name="runQueryAsAServiceResponse">

<s:complexType>

<s:sequence>

<s:element name="table" type="s0:Table" />

<s:element name="message" type="s:string" />

<s:element name="creatorname" type="s:string" />

<s:element name="creationdate" type="s:dateTime" />

<s:element name="creationdateformated" type="s:string" />

<s:element name="description" type="s:string" />

<s:element name="universe" type="s:string" />

<s:element name="queryruntime" type="s:int" />

<s:element name="fetchedrows" type="s:int" />

</s:sequence>

</s:complexType>

</s:element>

<s:element name="sessionID" type="s:string" />

</s:schema>

</types>

<message name="runQueryAsAServiceSoapIn">

<part name="parameters" element="s0:runQueryAsAService" />

</message>

<message name="runQueryAsAServiceSoapOut">

<part name="parameters" element="s0:runQueryAsAServiceResponse" />

</message>

<portType name="QueryAsAServiceSoap">

<operation name="runQueryAsAService">

<documentation>Get Web Service Provider server info</documentation>

<input message="s0:runQueryAsAServiceSoapIn" />

<output message="s0:runQueryAsAServiceSoapOut" />

</operation>

</portType>

<binding name="QueryAsAServiceSoap" type="s0:QueryAsAServiceSoap">

<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />

<operation name="runQueryAsAService">

<soap:operation soapAction="QaaWSTest/runQueryAsAService" style="document" />

<input>

<soap:body use="literal" parts="parameters" />

</input>

<output>

<soap:body use="literal" />

</output>

</operation>

</binding>

<service name="QaaWSTest">

<documentation />

<port name="QueryAsAServiceSoap" binding="s0:QueryAsAServiceSoap">

<soap:address location="http://eg-sapbod-z001/dswsbobje/qaawsservices/queryasaservice" />

</port>

</service>

</definitions>

[Former Member · Accepted solution]

hi,

your error message probably says ...QaaWSTest... instead of ...QssWSTest...

anyway, the [domcore spec|http://www.w3.org/TR/DOM-Level-2-Core/core.html#Namespaces-Considerations] states

...How relative namespace URI references are treated is undefined. To ensure interoperability only absolute namespace URI references (i.e., URI references beginning with a scheme name and a colon) should be used. ...

I suppose, SAP did suddenly enforce this rule but I weren't able to find the exact time either when this started (i.e. I didn't find a relevant note or release note elaborating on it).

IMHO, apart from your troubles this is a good move. relative namespaces do not make much sense.

hope it helps,

anton