As per the following section
25.1.13 Composites Calling Other Composites with Concrete WSDL Files
in Oracle documentation
If you use concrete WSDL files, be aware that the order of startup for SOA composite applications is not guaranteed.
For example, if one SOA composite application calls a second SOA composite application with a concrete WSDL file, and the first SOA composite application gets started before the second SOA composite application, an error occurs. This is because the first SOA composite application cannot load the second SOA composite application's WSDL file.
You can change the order to underlying module as per given in the Oracle documentation
section "Changing the Order of Deployment at Server Startup"
No comments:
Post a Comment