Hey
Aaron Mulder wrote:
> If you're in an entirely single-phase commit environment (outside
> of an app server) it would be a little bizarre to create this XAConnection
> abstraction on top of the Connections and then not use any of those
> features. It would just be an extra later of wrapping. Also, there would
> be overhead looking for non-existant transaction managers and potentially
> runtime errors if JNDI is not available.
> So I guess you're right that there's another approach, but we'd
> have to be very conscious to make the JNDI/transaction code modular, to
> return connections to the pool at the appropriate time (waiting for
> end() or not), and to minimize the extra overhead.
BTW, speaking of overhead. In a EJB context the "last used" scheme that
you had in the pools is quite overkill, since the usage is always short
(hence a timestamp on getConnection is sufficient).
So, at least for jBoss' purposes they could be simplified quite a bit in
this regard.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
