Database Reference
In-Depth Information
Windows. If the error on the standard output is not clear, we always recommend
reviewing the
out.err
file for additional information.
Most compilation errors are actually due to coding issues. In the preceding ex-
ample, one of the schemas in the project was importing a non-existent schema.
HelloWorldWebService.wsdl
had the following import statement:
<xs:import schemaLocation="http://externalserver/schema.xsd" namespace="http://soahost1/SOA/HelloWorldWebService"/>
Trying to access
http://externalserver/schema.xsd
returned an
HTTP
Error 503. The service is unavailable
error. Because this imported
schema was not available and could not be validated at compilation time, the
compilation subsequently failed, as expected.
Another common issue at compilation time is when you use the
oramds://
protocol to refer to external resources that are available in the metadata store.
Here, you can see that the composite build failed when
HelloWorld.xsd
,
which was being referenced from the MDS, was not loaded during compilation:
oracle.fabric.common.wsdl.SchemaBuilder.loadEmbeddedSchemas (SchemaBuilder.java:492) Caused by: java.io.IOException: oracle.mds.exception.MDSException:
MDS-00054: The file to be loaded oramds:/apps/Common/HelloWorld.xsd does not exist.
It is important to understand that at compilation time, ant would refer to an MDS
location that is configured in an
adf-config.xml
file. This file contains in-
formation to connect either a file or database based MDS. This file is available
at one of the following two locations:
•
Under the
[Composite_Home]\SCA-INF\classes\META-INF
project
folder where the MDS configuration is specific to a particular composite.
•
In the
[Application_Home]\.adf\adf-config.xml
file under the ap-
plication folder.
The following snippet is an example of the database based
adf-config.xml
.
This configuration file essentially tells your composite where your MDS is loc-
