Victor
That's a good question.
The thing I'd like to point out here is all (XA) compliant resources
need to register themselves with the TM. As part of their server
offerings vendors provide a way for commonly used resources eg.
DBConnections to register with the ongoing DT. However, for 3rd party OR
mapping vendors (I'm avoiding taking specific names) that rely on
transaction completion notifications to manage "their workspaces", they
require a transaction synchronizer object registered with the TM. This
really helps them use a standard way of achieving that.
Most common usages of OR mapping tools is found in Entity Beans. But it
is not difficult to imagine using them from Session Beans in which case
you still need this standard way of acessing the TM.
How do other server vendors handle this?
--
Harsh
GemStone Systems, Inc. A Brokat Company
"There is no faith which has never yet been broken,
except that of a truly faithful dog."
-- Konrad Z. Lorenz
> Harsh,
>
> Clearly, I'm not current on my spec reading. With the J2EE and EJB specs
> containing overlapping information, I'm not sure what applies where. Since your
> snippet is in Chaper 9 entitled "Entity Bean Component Contract for Container
> Managed Persistence" wouldn't that mean the java:pm context is only available to
> EJB 2.0 CMP Entity beans?
>
> --Victor
> > Not so fast my friend ...
> >
> > I did misspeak though. Spec I was meanig to refer to is EJB 2.0. To be
> > sure "Enterprise JavaBeans Specification, Version 2.0, Proposed Final
> > Draft, October 23, 2000".
> >
> > Look at page 202.
> >
> > A snippet -
> >
> > "The container provides an implementation of the TransactionManager
> > interface to the Persistence Manager through JNDI. The Persistence
> > Manager can locate the TransactionManager through the standard JNDI API
> > as java:pm/TransactionManager".
> >
> > -harsh-
===========================================================================
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".