Of course you guys may not be interested in supporting the spec any more, especially in its sillier aspects such as this one.
david jencks
On Tuesday, September 23, 2003, at 07:59 AM, Adrian Brock wrote:
On Tue, 2003-09-23 at 15:47, Bill Burke wrote:Adrian,
Are we removing the CachedConnectionInterceptor? We have code in place
to replace it?
No, but the processing is only really necessary for three reasons.
1) Nonshared resources
2) BMT code that does late transaction binding: DataSource.getConnection() UserTransaction.begin()
3) Connection close checking (a debug feature that can be turned off in production)
For more normal use it should have approx. zero impact
Regards, Adrian
Bill
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development-- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Director of Support Back Office JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
