Adapters Created in JDeveloper 188.8.131.52.0 with Message Header Variable Schema Structure Are Not Created Properly
(Doc ID 1262642.1)
Last updated on MARCH 12, 2019
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1]
Oracle JDeveloper - Version 18.104.22.168.0 to 22.214.171.124.0 [Release Oracle11g]
Information in this document applies to any platform.
Using JDeveloper 126.96.36.199.0, a composite application using 188.8.131.52.0 AQ and Apps Adapters in a BPEL Process is showing incorrect namespace information for the endpoints. The same process does not show this issue when using 184.108.40.206.0 JDeveloper.
Variables used in a copy statement are not showing the expected message structures.
In the image below, you can see that the From variable, "Variable_apps_header" has the same namespace reference and format as the To variable, "Variable_aq_header".
If you try to create a new variable based upon the message type for the Adapter, you will see that it is not properly formed.
In the image below, you can see that the variable, "Variable_apps_header" has the same namespace reference and format as the variable, "Variable_aq_header".
An examination of the Adapters' partnerLinkName.wsdl file shows incorrect information in the wsdl:definitions and schema tags.
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