Adapters Created in JDeveloper 11.1.1.3.0 with Message Header Variable Schema Structure Are Not Created Properly

(Doc ID 1262642.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle SOA Platform - Version: 11.1.1.3.0 to 11.1.1.3.0 - Release: 11gR1 to 11gR1
Oracle JDeveloper - Version: 11.1.1.3.0 to 11.1.1.3.0]
Information in this document applies to any platform.

Symptoms

Using JDeveloper 11.1.1.3.0, a composite application using 11.1.1.3.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 11.1.1.2.0 JDeveloper.

Symptom 1:

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".



Symptom 2:

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".


Symptom 3:

An examination of the Adapters' partnerLinkName.wsdl file shows incorrect information in the wsdl:definitions and schema tags.





Information regarding the example used in the images above.  In this case, the AQ Adapter was created before the Apps Adapter but the flow is like:


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