Hi Rob Use a DataSource - that way you are not worried about if the connection is pooled or not.
You will need to produce two factories for each datastore implemntation: #1: Take a DataSource in your DataStore constructor, the factory can make the connection (using whatever implementation you want like C3PO) #2: Take a JNDI name and use that to look up an already created DataSource , this what geoserver would use. For #1 above registering your DataSouce in JNDI would be a nice touch. Jody Rob Atkinson wrote: > I want to avoid dependencies on foreign JDBC drivers and use plain JDBC > connection URLs within connection pools. I'm afraid I didnt really > understand the comments that came back last time - it seems like stuff > was being considered but hasnt made it into a real implementation. > > There is a connection pool manager... in org.geotools.data.jdbc > > What is the current thinking on actually creating JDBC connection pools > however? > > Rob A > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Geotools-devel mailing list > Geotools-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
