"Request" suffix in element name of schema renames final WSDL message (Doc ID 1112710.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version: 8.1 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

You will notice that you get the same WSDL after generating Webservices artifacts from a WSDL which has the work "Request" in the element-name suffix:

WSDL snippet:
<wsdl:message name = "userImpairedTextSemanticValidationRequest">
   <wsdl:part element = "nsSchema:userImpairedTextSemanticValidationRequest"
              name = "body"/>
   <wsdl:part name = "Header" element = "head:Header"/>
</wsdl:message>

Schema snippet:
<xs:element name="userImpairedTextSemanticValidationRequest">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="CustomerNotification"
                  type="cst:CustomerNotificationForRequest"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

Execute with autotype and wsdl2service Ant tasks.

And if the client calls it with the original WSDL will get:

Tue Apr 20 16:54:11 CLT 2010:ERROR:An error occured [C:\ws-test\TextSemanticValidation-test2.wsdl:0: error: src-resolve.a: Could not find type 'userImpairedTextSemanticValidationRequest@http://test.it/SOA/TextSemanticValidation/2010-02-12'. Do you mean to refer to the element with that name?], see error log for details

Changes

None.

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