Databases Reference
In-Depth Information
Defining the 'PortType' Element
The final component of an abstract WSDL document is to define the
portType
and
its corresponding operations. For our
OrderFulfillment
service, we have defined
the following:
<portTypename="orderFulfilment">
<operationname="setShippingInstruction">
<inputmessage="tns:setShippingInstruction"/>
<outputmessage="tns:setShippingInstructionResponse"/>
</operation>
<operationname="submitInvoice">
<inputmessage="tns:submitInvoice"/>
<outputmessage="tns:submitInvoiceResponse"/>
</operation>
…
</portType>
Note that for the sake of brevity, we have only listed two operations; for the full set,
please refer to
OrderFulfilment.wsdl
contained within the sample application.
Using XML Schema and the WSDL within
SOA Suite
Once we have defined the abstract WSDL and corresponding XML Schemas, we are
ready to implement the services they define within the SOA Suite. These services will
typically be implemented as composites or proxy services within the Service Bus.
As we've seen in earlier chapters, the simplest way to use a predefined schema
within a composite is to import the schema from the filesystem into our SOA project.
When we do this, JDeveloper does two things. First, it will add a copy of the schema
file to our SOA project. Second, it will add an import statement into the WSDL of the
service component (for example, BPEL, Mediator) that is referring to it, for example:
<types>
<schemaxmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://rubiconred.com/obay/xsd/order"
schemaLocation="Order_v1_0.xsd" />
</schema>
</types>
