Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.5-M0
-
Component/s: unsupported
-
Labels:None
Description
Remove need for extended JDBC connectionPool and allow any old jdbc connection.
Remove wrappers.
This will also remove build dependency on Oracle and postgis (and any other wrapped) jdbc driver.
Issue Links
- is depended upon by
-
GEOT-564
JTDS (MS-SQL) JDBC driver in Geometryless module
-
- http://docs.codehaus.org/display/GEOTOOLS/J2EE+and+Connection+Pools
I have a bit of a testing plan in mind here:
- Create a MockDataSource (that still uses a DataSource) to make sure a DataSource registered JNDI actually works for GeoTools code (the root namespace is held by the GeoTools JNDI class)
- See if we can hunt down CP30 (the connection pool implementation used by JBoss) and use it in a test case
- See if we can hunt down DBCP (the connection pool used by Jetty?) and once again test
What do you think?