My Oracle Support Banner

WSDL Namespace Order is Different when it is used the ITEMSERVICEPORT?WSDL (Doc ID 2547624.1)

Last updated on MAY 29, 2019

Applies to:

Oracle SOA Suite - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

 Because the Setup Steps for ODI and Web Services to enable Publishing for Oracle Product Hub for Communications Release 12.2 (Doc ID 1336146.1) on 12.2.1.3.0 version was never tested by the Oracle Product Hub Development team. It was found that WSDL Namespace Order is Different when it is invoked the ITEMSERVICEPORT?WSDL:

For example:

SOATST ENV

Order of namespaces

ego/item/service

bom/structure/service/out

bom/structure/service/in

ego/item/service/out

ego/item/service/in

SOAPRR ENV

Soa_server1

ego/item/service

bom/structure/service/out

ego/item/service/out

bom/structure/service/in

ego/item/service/in

SOAPRR ENV

Soa_server2

ego/item/service

bom/structure/service/out

bom/structure/service/in

ego/item/service/out

ego/item/service/in

Issue is related with the different sort order on namespaces when WebService WSDL is invoked, hence this affects the SOA composites deployment that invoked this Out of the box WSDL.

This can be tested by just calling the WSDL from an internet browser pointing to a different manage server (host:port, same WSDL file), it can be observed the namespaces in different order.

Because this issue it is not possible to use this WSDL implementation on a SOA composite due the namespaces change everytime the WSDL is refreshed.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.