Re: [seam-dev] persistence module page drafted
On Wed, Apr 14, 2010 at 9:13 AM, Pete Muir <pmuir(a)redhat.com> wrote:
I'm with Emmanuel here.
All of this is addressable through an Transactions utiltiy class.
Let me ask for two clarifications that will help me understand the
counter
argument.
1. If this transaction wrapper extends UserTransaction, is that
worse/different than having a utility class? You can always inject the
native type, or inject the wrapper for the extra convenient status methods.
2. The transaction wrapper allows us reuse the UserTransaction API to
address JTA, resource-local and potentially spring transaction APIs as one.
The client then doesn't concern itself with which transaction API is being
used under the covers, but everyone "speaks" JTA UserTransaction. How do we
do that with just a utility class?
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
Attachments:
- attachment.html (text/html — 1.5 KB)