Databases Reference
In-Depth Information
In the
URL/Path
, enter the URL for our Echo WSDL. This is the
WSDL
location we
made a note of earlier (in the
WSDL
tab for the Echo process in the BPEL console)
and should look like the following:
http://<hostname>:<port>/orabpel/default/Echo/1.0/Echo?wsdl
Enter an appropriate value for the
Resource Name
(for example
Echo
), select a
Resource Type
as
WSDL
, and click on
Next
.
This will bring up the
Load Resources
window, which will list the resources that
OSB is ready to import.
You will notice that in addition to the actual WSDL file, it will also list the
Echo.xsd
.
This is because the
Echo.wsdl
contains the following import statement:
<wsdl:types>
<schema>
<import namespace=
"http://xmlns.oracle.com/SOASuiteBook11gChapter2_jws
/EchoComposite/EchoProcess"
schemaLocation=
"http://axreynol-us.us.oracle.com:8001/soa-infra/services/
default/EchoComposite/echoprocess_client_ep?
XSD=xsd/EchoProcess.xsd"/>
</schema>
</wsdl:types>
This imports the Echo XML schema, which defines the input and output message
of our Echo service. This schema was automatically generated by JDeveloper when
we created our Echo process. In order to use our WSDL, we will need to import this
schema as well. Because of the unusual URL for the XML Schema, the Service Bus
generates its own unique name for the schema.
