Subject | Re: Two XA bugs |
---|---|
Author | Ludovic Orban |
Post date | 2006-03-27T11:13:45Z |
David,
--- In Firebird-Java@yahoogroups.com, David Jencks <david_jencks@...>
wrote:
"An application programmer does not use this interface directly;
rather, it is used by a transaction manager working in the middle tier
server."
DataSource interface using XAConnection internally is the
responsibility of the container, not the JDBC driver.
Ludovic
--- In Firebird-Java@yahoogroups.com, David Jencks <david_jencks@...>
wrote:
> To reiterate and summarize:I agree. That's even written black on white in the XAConnection javadoc:
> -- Only someone who is writing a framework or container should be
> using ConnectionPoolDataSource or XADataSource directly.
"An application programmer does not use this interface directly;
rather, it is used by a transaction manager working in the middle tier
server."
> -- We should provide a miniature framework that exposes a DataSourceI disagree. I think that writing a connection pool that exposes
> and provides connection pooling and XA when a TransactionManager is
> provided.
DataSource interface using XAConnection internally is the
responsibility of the container, not the JDBC driver.
Ludovic