Hi: Sorry to raise the question again.
Recently , I check the EJB specification and do some test with ejb's container managed transaction-policy , also the spring-transaction template(they both are same) After checking and testing EJB, I think the camel's current transaction is deficiency; For example, EJB container transaction support such usage: Assuming EJB A invoke B. A, B used separate transaction(both is require-new policy); 1)If B failed then the B's transaction will rollback. 2) The caller A could choice to omit the B's exception and commit transaction, or not to omit B's exception and rollback transaction; But camel's transaction doesn't support such usage. This deficiency is caused by the camel's transaction-policy implementation mixed with error-handler. So if the camel's transaction implementation will not to use error-handler, the deficiency will be correct. If this worth to do in camel? Or there are some other reasons that camel 's transaction must use error-handler? Thanks any suggestion;
