WLS 10.3 - Clientgen Produces Different WSDL Elements for Complex Types after Upgrade from WebLogic 8.1 (Doc ID 1219293.1)

Last updated on JUNE 09, 2016

Applies to:

Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.

Symptoms

After webservice upgrade from Weblogic (WLS) 8.1 to 10.3, clientgen has changed some of the WSDL elements (eg. complex types).

Samples from WLS 8.1:

<s:complexType name="ListBean">
  <s:sequence>
     <s:element name="List" type="ope:List" minOccurs="0"/>
     <s:element name="Name" type="s:string" minOccurs="0"/>
     <s:element name="Array" type="ope:ArrayOfString" minOccurs="0"/>
   </s:sequence>
</s:complexType>

<s:complexType name="List">
  <s:sequence>
    <s:element name="item" type="s:anyType" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
  </s:sequence>
</s:complexType>

<s:complexType name="ArrayOfString">
   <s:sequence>
     <s:element name="String" type="s:string" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
  </s:sequence>
</s:complexType>


After upgrade to WLS 10.3, clientgen produces the following:

<xs:complexType name="ListBean">
  <xs:sequence>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="Array" nillable="true" type="xs:string"/>
    <xs:element minOccurs="1" name="List" nillable="true" type="java:List" xmlns:java="java:java.util"/>
  </xs:sequence>
</xs:complexType>

<xs:complexType name="List">
  <xs:complexContent>
    <xs:restriction base="soapenc:Array" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"/>
   </xs:complexContent>
</xs:complexType>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms