Opened 13 years ago
Closed 13 years ago
#586 closed enhancement (fixed)
Geotools (with spatial db) and geonetwork database should use same pool and add flexible JNDI
| Reported by: | simonp | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | v2.7.0 |
| Component: | General | Version: | |
| Keywords: | Geotools, database connections | Cc: |
Description
Currently GeoNetwork uses two database connection pools if using spatial database. Also JNDI option assumes tomcat Apache Commons DBCP. This patch adds a more flexible JNDI provider and uses one connection pool via Geotools.
Attachments (1)
Change History (2)
by , 13 years ago
| Attachment: | jndi.patch added |
|---|
comment:1 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Fixed in svn rev 8223 - JNDIPool.java (with example of how to use in WEB-INF/config.xml) allows geotools and geonetwork to use the same database pool with config in the container. JNDIPool also allows use of either shapefile or database for spatial index via provideDataStore config element - this is useful because at the moment we only support postgis for spatialindex but if you wanted to put the spatialindex in another database (eg. Oracle) then you can now add your own spatialindex table and then config GeoNetwork to use it.