Tammo, Grüß Gott. Forgive me, but that is almost the extent of the German I remember from when I was stationed in Ludwigsburg some 23 years ago. Meanwhile, I wanted to thank you for your quick response. However, one of the glaring omissions from the wonderful world of Apache is documentation.
You mentioned the "usePeer2Peer" attribute in the invoke element, but more importantly, you said that it is enabled by default. How would I call the process from my BPEL? I guess that is where I am getting hung up. -----Original Message----- From: Tammo van Lessen [mailto:[email protected]] Sent: Wednesday, April 17, 2013 7:30 AM To: user Subject: Re: Process-to-Process Invocation Hi Hendry, Process-to-process invocation is enabled by default, but you can configure it explicitly using the usePeer2Peer attribute in the invoke element in your deploy.xml. So actually it should just work. HTH, Tammo On Tue, Apr 16, 2013 at 11:00 PM, Hendry Betts < [email protected]> wrote: > Hello All, > > I am attempting to invoke an existing BPEL process from within a > different BPEL Process. Do I approach it as a PartnerLink or is there > some sort of "magic formula" I may be missing? Assistance would be greatly > appreciated. > > Hendry > > > ________________________________ > This electronic message transmission contains information from > GreenSky Trade Credit, LLC which may be confidential & privileged. > Recipients should not file copies of this e-mail with publicly > accessed records. The information is intended to be for the use of the > individual(s) named above. > If you are not the intended recipient, please be aware that any > disclosure, copying, distribution or use of this message is > prohibited. If you have received this electronic transmission in > error, please notify us by e-mail immediately. > -- Tammo van Lessen - http://www.taval.de This electronic message transmission contains information from GreenSky Trade Credit, LLC which may be confidential & privileged. Recipients should not file copies of this e-mail with publicly accessed records. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this message is prohibited. If you have received this electronic transmission in error, please notify us by e-mail immediately.
