Thank you for that, most helpful. The fact that SEDA and JCA flow
transactions can co-exist was not clear from the current docs.
There is no centralized point to handle transaction rollback /
redelivery, but std jbi components will catch all exceptions and mark the
transaction has rollback if there is an ongoing transaction and the exception is
a runtime
Ok, still a little unclear here. If a JCA-flow container fails and is
restarted, will all persisted exchanges resume once the container comes
back up? This implies heuristic rollback of uncommitted transactions.
I am trying to establish a once-and-only-once delivery QoS for my system
and where possible I would like to protect my business developers from
having to code specific transactional behaviour.
Terry
