In my BPEL service unit, there is the main BPEL, deploy.xml and several WSDL
files.  I want to find out how to produce deploy.xml and my WSDL files
efficiently (generate them?).  Thank you.

If you don't understand what I meant by my WSDL files, read the rest of this
email. My WSDL files differ from the original WSDL files that I download
from the web server (e.g. http://localhost:8192/PersonService/main.wsdl) in
the following aspects:

1. my WSDL files do not have <binding> and <service> tag.  The original WSDL
files do, as shown below.

- <#> <wsdl:binding name="*soapBinding*" type="*tns:Person*">
  <wsdlsoap:binding style="*document*" transport="*
http://schemas.xmlsoap.org/soap/http*"; />
- <#> <wsdl:operation name="*GetPerson*">
  <wsdlsoap:operation soapAction="" />
- <#> <wsdl:input>
  <wsdlsoap:body use="*literal*" />
 </wsdl:input>
- <#> <wsdl:output>
  <wsdlsoap:body use="*literal*" />
 </wsdl:output>
- <#> <wsdl:fault name="*UnknownPerson*">
  <wsdlsoap:fault name="*UnknownPerson*" use="*literal*" />
 </wsdl:fault>
 </wsdl:operation>
 </wsdl:binding>
- <#> <wsdl:service name="*PersonService*">
- <#> <wsdl:port binding="*tns:soapBinding*" name="*soap*">
  <wsdlsoap:address location="*http://0.0.0.0:8192/PersonService/*"; />
 </wsdl:port>
 </wsdl:service>

2.  My WSDL files have <partnerLinkType> additionally, as shown below.

   <plnk:partnerLinkType name="Person1LinkType">
       <plnk:role name="Provider" portType="tns:Person"/>
   </plnk:partnerLinkType>


--

Simon S.

Reply via email to