The data source referenced by the jta-data-source name is a
DataSource provided by the container in JNDI. It is the same one
that any application could look up and use, hence it is a
XADataSource is an internal type used by the driver and container to
coordinate XA, but users of the data source are not expected to
participate at that level. The JPA provider acts like a client of
the data source, using its connections to read and write, so it does
not need to be aware of the XA protocol being implemented underneath.
Hope this makes things clearer.
On 10/05/2012 7:50 AM, Christian Romberg wrote:
It is not explicitly mentioned in the spec, but I guess I can
safely assume, that the data source denoted by
jta-data-source is of type "javax.sql.XADataSource"?
After the JPA implementation has obtained an XAConnection from
this XADataSource, is it expected to
to do any calls (and if so, in any specific order) on this
E.g. is it necessary, to call XAConnection.getConnection() to
trigger that the app server calls XAConnection.getXAResource()
on the very same XAConnection? Or is it sufficient to just call
"XADataSource.getXAConnection()" to trigger this?
(Some background: we don't use JDBC connections (being not an ORM)
and probably we would need to provide our own
XADataSource implementation, so that the app server picks up our
own XAResource implementation)
| Versant GmbH
+49 40 60990-0
+49 40 60990-113
GmbH is incorporated in Germany. Company registration number:
54723, Amtsgericht Hamburg. Registered Office: Halenreie 42,
Hamburg, Germany. Geschäftsführer: Bernhard Wöbker, Volker John
NOTICE: This e-mail message, including any attachments, is for
use of the intended recipient(s) and may contain confidential or
proprietary information. Any unauthorized review, use,
distribution is prohibited. If you are not the intended
immediately contact the sender by reply e-mail and destroy all
the original message.