Hi,
I'm not sure yet what I think about adding it to cvs. I have two comments.
1. This would also be useful in case there is a "half-xa" driver that
supports 2pc but not sharing transactions accross connections. (natively,
firebird/interbase has supported 2pc since about 1984, but does not
currently share transactions across connections.)
2. Did you write/do you have the source to the resource adapter? I think a
better approach is to map all requests on a given transaction to a single
connection/cache inside the resource adapter. This is what I did with the
firebird driver I am working on. Even if technically xa-compliant, not
sharing a transactional cache when work comes in on several
ManagedConnections is surely not in the spirit of all the xa connection
sharing.
Comments?
David Jencks
On 2001.08.06 03:03:46 -0400 "Jung , Dr. Christoph" wrote:
> We have developed a pooling scheme that is a kind of hybrid between the
> SharedLocalTransactionCM and the
> XAConnectionManager ...
>
> Without tx context (read usage), the pool dispenses for each separate
> allocation request a different XA-enabled connection.
>
> Within a single tx context (read&write usage), the pool dispenses a
> single
> connection per factory for optimisation and cross-bean-instance
> coherence purposes (e.g., imagine a OR-mapping resource with a
> transactional
> in-memory cache per connection).
>
> Would anyone be interested in me polluting the org.jboss.pool.connector
> package with this?
>
> CGJ
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
