Re: ** IMPLEMENTATION.BPEL USERS ** - updated implementation-bpel code in trunk - affects your BPEL applications
I am cc'ing tunscay-users since this seems to be interesting to users and they may not be on the dev list. Thanks Mike. On 5/17/08, Mike Edwards [EMAIL PROTECTED] wrote: Folks, I've just committed some changes to the implementation-bpel and implementatio-bpel-ode code in trunk which fix some issues relating to exposing BPEL processes using Web services (and other remote protocols). These changes have an impact on the content of the deploy.xml file that is associated with your BPEL applications. In order to work correctly, you will need to ensure that your deploy.xml file corresponds to the following pattern: deploy xmlns=http://www.apache.org/ode/schemas/dd/2007/03; xmlns:tns=http://helloworld; xmlns:helloworld=http://helloworld; xmlns:greetings=http://greetings; xmlns:tus=http://tuscany.apache.org; process name=tns:HelloWorld activetrue/active provide partnerLink=helloPartnerLink service name=tus:helloPartnerLink port=HelloWorld/ /provide invoke partnerLink=greetingsPartnerLink service name=tus:greetingsPartnerLink port=Greetings/ /invoke /process /deploy You must ensure: a) Each partner link in your BPEL process is declared using either a provide.../ (for a service) or using a invoke.../ for a reference. b) Each provide/ and invoke/ must use the partnerLink name, as declared in your BPEL process. c) The provide/ and invoke/ elements each have a single child service/ element. The service/ elements have name and port attributes. The NAME attribute MUST be set to the same name as the partnerLink and MUST be prefixed by a prefix which references the namespace http://tuscany.apache.org; (tus in the example above). The port attribute can be set to any name (it must be present but it is not actually used for anything significant). Sorry for forcing this change on you all, but the previous version of the code had a mixup over the name of the services and references as used by the ODE BPEL engine - this change fixes that problem. In the next week, we shall aim to remove the need for the deploy.xml file entirely. All the information in the file is already known to the Tuscany code - either we shall generate the file dynamically, or - ODE willing - we shall pass the information to ODE in-memory, avoiding the need for a file at all. You will find that the BPEL Sample applications and the BPEL iTests have been adjusted to use this new format for the deploy.xml file. Yours, Mike.
Re: Implementation.bpel
Hi, See my answers in line: On 6/24/07, Luciano Resende [EMAIL PROTECTED] wrote: I have committed your initial patch for Tuscany-1365, and also provided a summary of the necessary steps to build ODE [1] for the ones interested on playing with the implementation at the moment. Perfect, thanks! One thing I noticed is that some required databases (ode-work/jpadb) is not being created (if not present)... is this a configuration issue as we were discussing on [2] or something that we need to investigate further ? Actually that's something I indicated in the bug report. The database is required if we want meaningful tests and for now it must be copied manually. I'll try to make Maven2 download it and unzip it somewhere, I just have to pay the time toll that goes with any non-trivial Maven2 task :) I'll try to have another patch ready today or tomorrow. Cheers, Matthieu [1] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+implementation.bpel [2] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg19068.html -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Implementation.bpel
As for the databases, if it helps, I have some places that I uploaded the derby db into src/test/resources [1]. This might be a workaround to have things working for the time being [1] https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/implementation-das/src/test/resources/ On 6/25/07, Matthieu Riou [EMAIL PROTECTED] wrote: Hi, See my answers in line: On 6/24/07, Luciano Resende [EMAIL PROTECTED] wrote: I have committed your initial patch for Tuscany-1365, and also provided a summary of the necessary steps to build ODE [1] for the ones interested on playing with the implementation at the moment. Perfect, thanks! One thing I noticed is that some required databases (ode-work/jpadb) is not being created (if not present)... is this a configuration issue as we were discussing on [2] or something that we need to investigate further ? Actually that's something I indicated in the bug report. The database is required if we want meaningful tests and for now it must be copied manually. I'll try to make Maven2 download it and unzip it somewhere, I just have to pay the time toll that goes with any non-trivial Maven2 task :) I'll try to have another patch ready today or tomorrow. Cheers, Matthieu [1] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+implementation.bpel [2] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg19068.html -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Implementation.bpel
Just to add Luciano in order to get a feel of deploying a simple Bpel Process in ODE, do check this module [1] bpel-test It contains various examples (like HelloWorld etc..) where in required .bpel / .wsdl / deploy.xml are put in a directory [2] and the entire directory is deployed. The request / response expected from the bpel process are available in test.properties . This [3] will give a broad idea of when/how ode runtime is initialized , made to run , deployed and finally invoked. [1] - http://svn.apache.org/repos/asf/incubator/ode/trunk/bpel-test/ [2] - http://svn.apache.org/repos/asf/incubator/ode/trunk/bpel-test/src/test/resources/bpel/2.0/HelloWorld2/ [3] - http://svn.apache.org/repos/asf/incubator/ode/trunk/bpel-test/src/main/java/org/apache/ode/test/BPELTestAbstract.java ~~ Sam... _ On 6/25/07, Luciano Resende [EMAIL PROTECTED] wrote: Hi Matthieu I have committed your initial patch for Tuscany-1365, and also provided a summary of the necessary steps to build ODE [1] for the ones interested on playing with the implementation at the moment. One thing I noticed is that some required databases (ode-work/jpadb) is not being created (if not present)... is this a configuration issue as we were discussing on [2] or something that we need to investigate further ? [1] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+implementation.bpel [2] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg19068.html -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --
