<?xml version="1.0" encoding="UTF-8"?>
<definitions name="FlightPlan" targetNamespace="
http://j2ee.netbeans.org/wsdl/FlightPlan"
xmlns="
http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:tns="
http://j2ee.netbeans.org/wsdl/FlightPlan" xmlns:ns="
http://xml.netbeans.org/schema/FlightPlanSchema" xmlns:plnk="
http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:file="
http://schemas.sun.com/jbi/wsdl-extensions/file/">
<types>
<xsd:schema targetNamespace="
http://j2ee.netbeans.org/wsdl/FlightPlan">
<xsd:import namespace="
http://xml.netbeans.org/schema/FlightPlanSchema" schemaLocation="FlightPlanSchema.xsd"/>
</xsd:schema>
</types>
<message name="FlightPlanOperationRequest">
<part name="source" element="ns:FlightPlan"/>
</message>
<message name="FlightPlanOperationReply">
<part name="result" element="ns:AvailableFlights"/>
</message>
<portType name="FlightPlanPortType">
<wsdl:operation name="FlightPlanOperation">
<wsdl:input name="input1" message="tns:FlightPlanOperationRequest"/>
<wsdl:output name="output1" message="tns:FlightPlanOperationReply"/>
</wsdl:operation>
</portType>
<binding name="FlightPlanBinding" type="tns:FlightPlanPortType">
<file:binding/>
<wsdl:operation name="FlightPlanOperation">
<file:operation/>
<wsdl:input name="input1">
<file:message use="literal" fileName="FlightPlanData_%d.xml" pollingInterval="1000" fileNameIsPattern="true"/>
</wsdl:input>
<wsdl:output name="output1">
<file:message use="literal" fileName="FlightPlanOut.xml" multipleRecordsPerFile="true" recordDelimiter="\n" fileNameIsPattern="false"/>
</wsdl:output>
</wsdl:operation>
</binding>
<service name="FlightPlanService">
<wsdl:port name="FlightPlanPort" binding="tns:FlightPlanBinding">
<file:address fileDirectory="C:\Temp"/>
</wsdl:port>
</service>
<plnk:partnerLinkType name="FlightPlan1">
<!-- A partner link type is automatically generated when a new port type is added. Partner link types are used by BPEL processes.
In a BPEL process, a partner link represents the interaction between the BPEL process and a partner service. Each partner link is associated with a partner link type.
A partner link type characterizes the conversational relationship between two services. The partner link type can have one or two roles.-->
<plnk:role name="FlightPlanPortTypeRole" portType="tns:FlightPlanPortType"/>
</plnk:partnerLinkType>
</definitions>
[Message sent by forum member 'kagdemahesh' (kagdemahesh)]
http://forums.java.net/jive/thread.jspa?messageID=237075