Hey
Aaron Mulder wrote:
> True - except in the case of stateful session beans. In that
> case, I think the user can control when to end the transaction (even
> spanning several EJB invocations).
You're not paying attention ;-) The work is tied to the tx not the
connection. So the use of the *connection* will always be short-lived.
I.e.
* start tx
* use con
.. time passes
* use con
.. time passes
* use con
* commit tx
So even though the tx itself is taking a really long time, the use of
the connections is short, hence no need for timestamping on every
action. Just getConnection.
> So perhaps we could include a
> parameter to disable last used updates - really, in a stateless or entity
> bean, the last used time might as well be when the connection was checked
> out of the pool.
Correct. Although I would skip it for all operations except
DataSource.getConnection
Your call :-)
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
