Thanks for the informative discussion .. as promised here is my tough plan: - http://docs.codehaus.org/display/GEOTOOLS/J2EE+and+Connection+Pools
Currently I only have scope to fix this problem for EPSGDefaultFactory ... I have outlined the plan for JDBCDataStore as well. Cheers, Jody Jody Garnett wrote: > Thanks Andrea! That was a great overview of the trade-offs. > > I am looking at how we do connection pools in GeoTools - but more > towards JNDI lookup then > handling of prepared statements. Is there anything you would like me to > look out for when > I do this work? > > It sounds from your email that a shared connection pool in a J2EE > setting (ie shared with > other web applications) may result in a glut of cached prepared statements? > > Jody > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
