EJB has no dependency on JTS. EJB only depends
on the javax.transaction.UserTransaction interface defined in JTA,
and the transaction exceptions defined in javax.transaction.
The EJB server may, but does not have to, choose to use
JTS when implementing a transaction manager.
Vlada
-----Original Message-----
From: Chris Raber <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, March 02, 1999 6:19 PM
Subject: Re: JTA and JTS in EJB
>One can provide a JTS interface without actually provided real distributed
>transactions. Some EJB servers have a real distributed transaction
>service and some don't.
>
><vendor pitch>
>GemStone/J does
></vendor pitch>
>
>-Chris.
>
>> -----Original Message-----
>> From: Nishi Nidamarty [SMTP:[EMAIL PROTECTED]]
>> Sent: Tuesday, March 02, 1999 5:18 PM
>> To: [EMAIL PROTECTED]
>> Subject: JTA and JTS in EJB
>>
>>
>> Hi All,
>>
>> Trying to get a picture of how an App server supports user demarcated
>> transactions.
>> For this user need to make an explicit call to
>> "javax.jts.UserTransaction.begin()", so this is thru JTS. I remember
>> reading somewhere in the docs from Java Soft, that an implementation of
>> JTS is not needed in EJB by default unless the server plans to support
>> distributed transactions.
>> And in the EJB spces pg 95 "The javax.jts.UserTransacion interface is
>> the only JTS interface that the EJB container provider must implement in
>>
>> order to support EJB"
>>
>> Does it mean client demarcated transactions are not distributed ?
>> Is it becos we want our client to work on any transaction manager we use
>>
>> this interface ?
>> (so at later time though we change our backend TX-service we need not
>> change the application)
>> Does the container need to know of any client initiated transactions ,
>> or does it go thru TS directly ?
>> How does the container keep track of all the EB's involved in a single
>> transaction started by the client ?
>>
>> My understanding of JTA and JTS :
>> JTA is used by EJB applications to communicate with a TX service, if we
>> don't support distributed transactions (which seems not to be a
>> requirement of EJB) and have just one TX service then is JTA is good.
>> On the other hand if we have more than on TX manager, TP monitors, ...
>> then we need JTS for interoperability.
>> Any thoughts/clarifications on
>> Where do we need JTA and when do we need JTS ?
>>
>> Thanks!!!
>> Nishi.
>>
>> --
>>
>>
>> --
>>
>> (| (.)(.)|)
>> -------------------OOOo--()--oOOO.---------------
>>
>> Nishi Nidamarty TDI Inc. ,
>> TEL : 408-330-3466 5000 Old IronSides Dr,
>> FAX : 408-330-3444 Santa Clara CA 95054.
>>
>> <mailto:[EMAIL PROTECTED]> <http://www.tdiinc.com>
>> ------------------------------------------------------------
>>
>
>===========================================================================
>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".
>
>
===========================================================================
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".
