Kevin Dick wrote:
>
> Sriram Srinivasan wrote:
> >
> > "Brian N. Miller" wrote:
> > > How "real" are Tengah's distributed transactions?
> >
> > Real enough. It goes through the whole two phase commit process (4 phases
> > if you include preprepare and postcommit). The JDBC driver supplied,
> > on the other hand, don't support XA.
> >
> > -Sriram
>
> What precisely does this combination of features mean for the propagation of
> distributed transactions from the application server to backend databases?
> Are you saying that WebLogic can handle distributed transactions at the
> application level, but cannot then manage (as an OTS or XA coordinator)
> distributed transaction across the affected data sources?
Weblogic's JTS has most of the infrastructure in place (in active use)
for distributing a transaction across servers. It has Resources,
Coordinators, Control, Current, all the interfaces that you see in
CORBA OTS. It also has an internal service provider implementation
to make use of another tm system such as DTC or Tux.
What we *currently* don't supply is any XA resources that go with it,
precisely because XA support is so badly broken in different dbs (in
multi-threaded environments). This is changing rapidly as we speak ..
expect the Weblogic Enterprise server to have true distributed
transactions using the native Tuxedo implementation.
-Sriram
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
