Databases Reference
In-Depth Information
Defining a common interface
While we can override the endpoint for a partner link, all other attributes of our
service definition remain fixed. So to use this approach, we must define a common
interface that all of our
Job
services will implement. For our purposes, we've defined
the following abstract WDSL:
<?xmlversion="1.0"encoding="UTF-8"?>
<definitionsname="Job">
<types>
<schema>
<importnamespace="http://rubiconred.com/obay/xsd/schedule"
schemaLocation="../schedule.xsd"/>
<elementname="executeJob"type="client:ExecuteJob"/>
<complexType name="ExecuteJob">
<sequence>
<element name="job" type="sch:Job"/>
</sequence>
</complexType>
</schema>
</types>
<messagename="executeJob">
<partname="payload"element="tns:executeJob"/>
</message>
<portTypename="Job">
<operationname="executeJob">
<inputmessage="tns:executeJob"/>
</operation>
</portType>
<plnk:partnerLinkTypename="Job_PL">
<plnk:rolename="Job_Role">
<plnk:portTypename="tns:Job"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
