Jarvis Pizzeria: Send Task vs Throw Message Event by Richard Olrichs & Marcel van de Glind & Marc Kuijpers
October 11, 2018 Leave a comment
Now that many of you are acquainted implementing BPM(N) processes, one should have noticed that there are multiple roads leading to the same goal while implementing a business process. One example is the invocation of an asynchronous service. This can either be done with a Send Task or a Message Throw Event. This blog tells about the difference between those two activities within PCS and when you should pick one over the other.
Let’s discuss the Send Task first. The Send Task lets you: instantiate a process, trigger a Receive Task in the middle of a process, or trigger a Message Catch event. Furthermore, the Send Task allows to attach boundary events to it. In other words, you can either attach an error boundary event to a Send Task as well as a Timer Catch Event. The former implies that the process that is invoked by the Send Task propagates its faults to the calling process.
How about the Message Throw Event? Well, it is nearly the same as the Send Task except that one is not able to attach boundary events to it and the calling process won’t be notified upon failures in the called process. Read the complete article here.
For regular information on Oracle PaaS become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog
Twitter
LinkedIn
Facebook
Wiki
Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress