>> By the spec each finder must query the database. Too sad. Is this really so? This is a very peculiar thing to write into a spec. Usually, spec statements tend to be less concrete, leaving vendors room for optimizations... If the above statement is indeed in the spec, someone should change it. Resultset caching is too nice a thing to leave it out of J2EE. ;(
mikea-xoba: >> as the other gentleman pointed out *g the who? the what?! Jboss does not cache resultsets but c-jdbc does. C-JDBC is an open-source framework for db clustering and offers support for resultset caching as well. For one thing you could use c-jdbc as an intermediate layer between jboss and your database to add resultset caching capabilities. Furthermore, provided that the c-jdbc algorithm for resultset-caching is valid, it might serve as a prove-of-concept that such a thing is possible. Hmm, c-jdbc even deals with clustered dbs, but on the other side also makes the assumption that all db accesses happen through jdbc connections... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3823636#3823636 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3823636 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
