Question

2
Replies
85
Views
Manuel Trumm (ManuelT6)
Atos IT Solutions and Services GmbH

Atos IT Solutions and Services GmbH
DE
ManuelT6 Member since 2014 1 post
Atos IT Solutions and Services GmbH
Posted: January 31, 2018
Last activity: February 6, 2018
Posted: 31 Jan 2018 3:23 EST
Last activity: 6 Feb 2018 10:30 EST
Closed

Own Types in Pega service generated WSDL

Building a Pega service. Tried from scratch (classes, properties, parse, stream) as well as from XSD. After creating the service package and testing the service successfully, the generated WSDL embeds complex types instead of naming the types, example:

Generated WSDL excerpt:

<complexType name="ServiceRequest">
  <sequence>
    <element name="Application">
      <complexType>
        <sequence>
          <element name="PegaID" type="string"/>
          <element name="PegaApplication" type="string"/>
        </sequence>
      </complexType>
    </element>
  </sequence>
</complexType>

Desired WSDL excerpt:

<complexType name="ApplicationInformation">
  <sequence>
    <element name="PegaID" type="string"/>
    <element name="PegaApplication" type="string"/>
  </sequence>
</complexType>
<complexType name="ServiceRequest">
  <sequence>
    <element name="Application" type="tns:ApplicationInformation"/>
  </sequence>
</complexType>

The desired WSDL allows to re-use complex types. But Pega's generated WSDL just repeats the definition, if the complex type is used in another place. The problem is then the Service client, that cannot reuse the complex types.

So, the question is how to achieve the desired WSDL.

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.