Database Reference
In-Depth Information
The preceding screenshot shows a version specific abstract WSDL, which is:
http://soahost1:8001/soa-infra/services/default/Hel-
loWorld!1.0/HelloWorld.wsdl
.
The default version can be referenced as follows:
http://soahost1:8001/soa-infra/services/default/Hel-
loWorld/HelloWorld.wsdl
Here, it is the responsibility of the developer to make this change and ensure
that references are made to abstract versus concrete WSDLs.
Consider another scenario where you have multiple composites deployed to
your infrastructure and they refer to each other to achieve a business function.
During server startup, if one composite A calls another composite B with a con-
crete WSDL file, and composite A starts up before composite B, you will get
the same error as shown earlier. This is because composite A is unable to load
composite B's WSDL file, which is not yet available. Unfortunately, in Oracle
SOA Suite 11g, it is not possible to control the order in which composites are
loaded. In this case too, the same solutions that were discussed earlier apply.
The second approach is preferred so as to save repetitive activation of compos-
ites every time.
