Unable to Generate Proxy with <xsd:complexContent>

[Former Member]

We are trying to consume a webservice which has a ComplexContent

tag/element and uses extension base. The elements under complex content

are not visible to the SAP ABAP Client/Proxy Generator but is present

in the WSDL. This limits us from consuming the webservice.

<b>Has anybody faced thsi kind of problem ?</b>

We are not equipped to use the SAP netweaver Developer Studio (NWDS) yet!

In the segment of the WSDL attached below :

DCTMDoc element is recognised by the Proxy generator, but

SAPElisArtwork which extends DCTMDoc is not seen by the SAP ABAP Proxy

generator. This has become a major limitation consuming the webservice

because one of the methods accepts SAPElisArtwork as it's input

parameter.

Portion of the WSDL is below :

- <xsd:element name="elisCreate">

- <xsd:complexType>

- <xsd:sequence>

<xsd:element xmlns:tp="java:com.wyeth.elis.services.ws.common" type="tp:ElisServiceCredentials" name="credentials" />

<xsd:element xmlns:tp="java:com.wyeth.elis.services.ws.common" type="tp:DCTMDoc" name="docProps" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

- <xsd:element name="elisCreateResponse">

- <xsd:complexType>

- <xsd:sequence>

<xsd:element xmlns:tp="java:com.wyeth.elis.services.ws.common" type="tp:ElisResult" name="results" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

..... continued...

<xsd:complexType name="DCTMDoc">

- <xsd:sequence>

<xsd:element type="xsd:string" name="ownerName" minOccurs="1"

maxOccurs="1" nillable="true" />

<xsd:element type="xsd:string" name="title" minOccurs="1"

maxOccurs="1" nillable="true" />

</xsd:sequence>

</xsd:complexType>

- <xsd:complexType name="SapElisArtwork">

- <xsd:complexContent>

- <xsd:extension base="stns:DCTMDoc">

- <xsd:sequence>

<xsd:element type="xsd:string" name="componentType" minOccurs="1"

maxOccurs="1" nillable="true" />

<xsd:element type="xsd:string" name="componentTypeCode" minOccurs="1"

maxOccurs="1" nillable="true" />

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

[Former Member]

Hi,

I have the same issue. Did you find a solution ?

Thanks in advance.