Re: which transaction to be used ?
gk wrote:
still, i dont understand a concrete difference what JTA can do but
JDBC *cant* do.
so can i assume JTA is a suprior API because it offers more flexibilty
and there is no such big difference between JDBC trans and JTA trans
........JTA offers ease and comfortability.
i doubt this conclusion though....there must be some difference
Did you read my entire reply? JTA is concerned with more than just
databases, it is concerned with resources. So any resource in a system
that is supported by the local transaction manager and jta can be part
of a transactional context. jta transactions start at the app level not
the dba level, so objects, beans etc can be part of the transaction and
the scope is determined at the app level.
Database wise JTA just makes it a lot simpler to use distributed
transactions, just because all the plumping code is already done for
you. And that is a lot of the point in j2ee, that the plumbing code and
support code (libraries, apis etc) is pre-done by someone else, so you
dont have to invent the wheel every single time.
tom