For persistence and transactionality, you can use cascading JMS queues to link your process steps in a sequence, such that messages will only be ACK'ed or transactions will commit if that step of the process succeeded.
And for human task processing, BPEL doesn't provide a solution anyway. Some extensions such as BPEL4People and WS-HumanTask aimed to define a standard interface for workflow engines to plug into BPEL processes. However, the solution that ended up gaining more traction in this area was BPMN2. Do you have any steps involving humans or manual workflow in your processes? Regards, Raúl. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-vs-BPEL-tp5719214p5719459.html Sent from the Camel - Users mailing list archive at Nabble.com.
