> Nishi Nidamarty wrote:
>
> 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"
The correct package name is javax.transaction.UserTransaction. Theuse of
javax.jts.UserTransaction is deprecated in the next EJB spec
release. Please refer to the JTA spec for more information on using
the UserTransaction interface in EJB client and bean applications.
The JTA 1.0 spec is downloadable from:
http://java.sun.com/products/jta
> Does it mean client demarcated transactions are not distributed ?
No. Distributed transaction capability is not exposed to the
application. Transaction context propagation is performed "behind the scene".
> 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)
The application server interacts with the Transaction Manager to provide
transaction support in EJB. The EJB bean uses the EJB API to obtain a
reference to UserTransaction (via the EJBContext.getUserTransaction method).
> Does the container need to know of any client initiated transactions ,
> or does it go thru TS directly ?
The container needs to know if an EJB instance is invoked withclient
transaction. One implementation is through the use of the JTA's
TransactionManager.getTransaction method. Other implementations
might use private interfaces between the container and the TM.
> How does the container keep track of all the EB's involved in a single
> transaction started by the client ?
The actual transaction management is done by the Transaction Manager.
> 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 ?
>
Take a look at the JTS 0.95 spec, it addresses some of your questions.
http://java.sun.com/products/jts
Susan
> 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".
