The BPM provider allows Mule events to initiate and/or advance processes in an
external or embedded Business Process Management System (BPMS). It also allows
executing processes to generate Mule events.
This field will be used to correlate messages with processes.
The global receiver allows an endpoint of type "bpm://*" to receive any
incoming message to the BPMS, regardless of the process. If this is false, the
process name must be specified for each endpoint, e.g. "bpm://MyProcess" will
only receive messages for the process "MyProcess".
If false, any message generated by the process is routed from the service on
which it is received. If true, a process can send messages to any endpoint
on any service.
This method looks for a receiver based on the process name and ID. It searches
iteratively from the narrowest scope (match process name and ID) to the widest
scope (match neither - global receiver) possible.
- ProcessMessageReceiver or null if no match is found
Generate a URL based on the process name and ID such as "bpm://myProcess/2342"
If the parameters are missing, and
the GLOBAL_RECEIVER is returned.
"No valid URL could be created for the given process name and ID: processName = " + processName + ", processId = " + processId);
+ ", processId = " + processId));