That's very useful to know! Thank you so much :o)
On Mon, Oct 18, 2010 at 12:16 PM, Denis Weerasiri <[email protected]> wrote: > On Mon, Oct 18, 2010 at 10:27 PM, Luis Miguel Silva < > [email protected]> wrote: > >> Dear Denis, >> >> Thank you for your reply. >> I did now my deploy.xml was incomplete, but Eclipse's BPEL editor did >> not allow me to fill it in (directly using the editor) and that is why >> i was feeling kind of lost. >> >> Thank you for your example. >> >> I would also like to ask you what do you mean by having that external >> web service stored locally? Do you mean i have to download the WSDL >> for all external web services and reference them using local WSDL >> files? >> > Yp, IIRC, the WSDLs need to be local. > >> >> Thank you! >> Luis >> >> On Mon, Oct 18, 2010 at 10:37 AM, Denis Weerasiri <[email protected]> >> wrote: >> > Hi Luis, >> > I looked in to the attached bpel. >> > First I looked into the deploy.xml. It contains no elements like >> <provide/> >> > <invoke/> elements. Every partner link used with a <receive /> activity >> must >> > be matched with a <provide /> element, and every partnerLink used in an >> <invoke >> > /> activity must be matched with an <invoke /> element in deploy.xml. >> > Without a deploy.xml, a BPEL engine cannot figure the concrete level >> details >> > of the partner services. In the deploy.xml, the <service /> element >> > determines the concrete level details of all the partner services that >> > interacts with the BPEL process. >> > >> > eg - >> > >> > <?xml version="1.0" encoding="UTF-8"?> >> > <deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03" >> > xmlns:FunctionProcess.bpel="http://FunctionProcess.bpel" >> > xmlns:FunctionProcessService.wsdl=" >> http://FunctionProcessService.wsdl" >> > xmlns:AdderService.wsdl="http://AdderService.wsdl" >> > xmlns:MultiplierService.wsdl="http://MultiplierService.wsdl" >> > xmlns:SquareService.wsdl="http://SquareService.wsdl"> >> > <process name="FunctionProcess.bpel:FunctionProcess"> >> > <process-events generate="all"/> >> > <provide partnerLink="FunctionProcessPartnerLink"> >> > <service >> name="FunctionProcessService.wsdl:FunctionProcessServiceService" >> > port="FunctionProcessServicePort"/> >> > </provide> >> > <invoke partnerLink="SquarePartnerLink"> >> > <service name="SquareService.wsdl:SquareService" >> > port="SquareServiceSOAP11port_http"/> >> > </invoke> >> > </process> >> > </deploy> >> > >> > So the http://services.sapo.pt/Metadata/Contract/ADSL?culture=PT also >> should >> > be stored locally. >> > >> > There may be other issues as well. >> > >> > >> > On Sat, Oct 16, 2010 at 2:09 AM, Luis Miguel Silva < >> > [email protected]> wrote: >> > >> >> Dear all, >> >> >> >> I just found out about Apache ODE this week and i've been extremely >> >> excited for its capabilities! (so i would like to start by >> >> congratulating and showing my appreciation by all the developers :o)). >> >> >> >> I've been playing around with Eclipse BPEL and was able to deploy a >> >> sample "hello world" program (following this tutorial -> >> >> http://www.eclipse.org/bpel/users/pdf/HelloWorld-BPELDesignerAndODE.pdf >> ) >> >> but i have a lot of questions on how to interface with an actual >> >> external web service. >> >> I've been reading a lot and could not find a good top / down example >> >> on how to interface with an external web service, use multiple input >> >> variables and multiple output variables, as well as how to convert >> >> between different types [i.e. i get a boolean result but want to shove >> >> it into a string] (i know i'll have to use xPATH to do it but it is >> >> still not clear to me how it works as, even just using the Eclipse >> >> BPEL designer, i still get a lot of bizarre errors). >> >> >> >> I ended up creating a very simple project with an if statement that >> >> tries to understand the value of the boolean variable and correctly >> >> populate the string one and, although Eclipse does not complain about >> >> any errors, the Apache ODE Deployment Descriptor does not seem to >> >> recognize the WDSL definitions for my project...ARGH! >> >> "Description Resource Path Location Type >> >> No grammar constraints (DTD or XML schema) detected for the >> >> document. deploy.xml /myproject/bpelContent line 1 XML >> Problem >> >> " >> >> It's also not entirely clear to me what the difference is between a >> >> global or local variable / partner link? >> >> >> >> Does anybody know any good tutorials that go into a little more detail >> >> than the one i mentioned above? >> >> I'm interested in learning to both use the Eclipse BPEL designer and >> >> defining the BPEL packages myself. >> >> >> >> I've attached my sample project to this email. I would be extremely >> >> grateful if someone can help me understand what am i doing wrong and >> >> point me on the right direction! >> >> This project just tries to consume an external web service (as >> >> described here -> >> >> http://services.sapo.pt/Metadata/Contract/ADSL?culture=PT) and return >> >> "true" or "false" based on that service's reply. >> >> I would really love to see a couple of more complex examples on how to >> >> throw exceptions, conditions, passing a variable number of inputs >> >> (which is another thing i DO NOT understand how to do), etc. >> >> >> >> Thanks a lot my friends, >> >> Luis Silva >> >> >> > >> > >> > >> > -- >> > Thanks, >> > Denis >> > ---------------------------------------------------------- >> > *Denis Weerasiri* >> > <http://wso2.com/>**** <http://wso2.com/>* blog: ** >> > http://ddweerasiri.blogspot.com* <http://ddweerasiri.blogspot.com/>* >> > twitter: **http://twitter.com/ddweerasiri* < >> http://twitter.com/ddweerasiri>* >> > linked-in: **http://lk.linkedin.com/in/ddweerasiri*< >> http://lk.linkedin.com/in/ddweerasiri> >> > >> > > > > -- > Thanks, > Denis > ---------------------------------------------------------- > *Denis Weerasiri* > <http://wso2.com/>**** <http://wso2.com/>* blog: ** > http://ddweerasiri.blogspot.com* <http://ddweerasiri.blogspot.com/>* > twitter: **http://twitter.com/ddweerasiri* <http://twitter.com/ddweerasiri>* > linked-in: > **http://lk.linkedin.com/in/ddweerasiri*<http://lk.linkedin.com/in/ddweerasiri> >
