[CAMEL-10685] TransactionErrorHandler and TransactionPolicy for Camel CDI / JavaEE

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.19.0
• Component/s: camel-cdi
• Estimated Complexity: Unknown
• Assignee: Antonin Stefanutti
• Reporter: RasPelikan
• Created: 10/Jan/17 11:08
• Updated: 14/Apr/17 07:26
• Resolved: 13/Apr/17 14:54

Description

The "transacted" configuration requires a Spring environment. We use JavaEE and we needed to use "transacted". We ported the Spring implementation of the TransactionErrorHandler to JavaEE.

There is only one major difference: Spring's TransactionErrorHandler derives from org.apache.camel.processor.RedeliveryErrorHandler which brings the behavior that redelivery is done within the transaction. In our implementation there is a RedeliveryErrorHandler which uses the TransactionErrorHandler to force a rollback and create a new transaction for each redelivery.

Example usage:

errorHandler(transactionErrorHandler() //
                .setTransactionPolicy("PROPAGATION_SUPPORTS") //
                .maximumRedeliveries(5) //
                .maximumRedeliveryDelay(5000) //
                .collisionAvoidancePercent(10) //
                .backOffMultiplier(1.5));
from("direct:sample") //
                .transacted("PROPAGATION_REQUIRES_NEW")
                .to("bean:sampleBean");

Issue Links

• links to: GitHub Pull Request #1390