CODEWITHSUNDEEP
design-patternsarchitecturejakarta-eetransactionsmessaging
Tomasz Blachowicz
Tomasz Blachowicz

Reputation: 5853

How to name the following pattern based on messaging and unit of work (XA)?

I'm having a difficulty with naming the pattern used commonly by the application I've been working on for a while. Just to set the scene: this is a Java EE application that uses messaging (JMS) a lot, persist data in relational database (JDBC) and relies on global transactions (XA) managed by the application server (JTA).

The pattern I'm talking about can be described as follows:

In case of the uncaught exception the ongoing unit-of-work is being rolled back and the original message that triggered the process goes back to the queue for redelivery.

So, the question is how would you name such a pattern? Unfortunately I'm not aware of any good name for such a pattern, but I wouldn't be surprised if the pattern has already been names nicely.

Upvotes: 2

Views: 209

Answers (2)

Guy Pardon
Guy Pardon

Reputation: 494

Transactional client indeed.

However, you could try the Atomikos variant, message-driven POJOs. It will take the burden of transaction control off of your application's back and results in much simpler code.

See http://www.atomikos.com/Publications/J2eeWithoutApplicationServer for more details.

HTH Guy

Upvotes: 0

markusk
markusk

Reputation: 6677

In the Enterprise Integration Patterns book by Gregor Hohpe and Bobby Woolf, this is simply called "Transactional Client".

Upvotes: 2

Related Questions