Wrong namespace in generated transformation

[#1]

Hi Guys.

I'm stuck for quite a while now figuring out why my consumer proxy does not map XML-Response into ABAP-Structure.

Finally i found that the generated simple transformation is expecting a namespaced node (<n1:response ..>).
But the original response from the webservice is just delivering (<response>).

Is there a possibility to define the WSDL in such a way, that generated simple transformation is not expecting a <n1:response> node?
(Additional info: the next node in the WSDL <AccessData> does not own a namespace in the simple transformation!)

Thanks for any help,

Timo

Following a snippet from the simple transformation

<tt:ref name="ROOT">

...

<tt:ref name="ROOT">

And the corresponding parts of the WSDL file:

          <xsd:complexType name="__SearchAccessResponse">

            <xsd:sequence>

              <xsd:element name="AccessData" nillable="true" type="tns:__AccessItem" minOccurs="0"/>

              <xsd:element name="errorCode" nillable="true" type="xsd:string" minOccurs="0"/>

              <xsd:element name="errorMessage" nillable="true" type="xsd:string" minOccurs="0"/>

            </xsd:sequence>

          </xsd:complexType>

          <xsd:complexType name="__AccessItem">

            <xsd:sequence>

              <xsd:element name="item" nillable="true" type="tns:__AccessEntry" minOccurs="0" maxOccurs="unbounded"/>

            </xsd:sequence>

          </xsd:complexType>

...

          <wsdl:message name="_searchAccessOutput" xmlns="">

          <wsdl:part name="response" type="tns:__SearchAccessResponse"/>

         </wsdl:message>

[Former Member]

In the end I called the proxy class, got the XML-Payload over the protocol interface and used an own simple transformation to fill the output structure. So if the WSDL file will some day be generated in the correct way, I just remove the couple of additional lines and everything still works and will be fine.

Thanks for trying to help.

Timo.