Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 3.04
-
Fix Version/s: 3.05
-
Component/s: Referencing
-
Labels:
Description
The EPSG factories in Geotk do not declare any dependency to a JDBC driver on intend, in order to let the user choose his database engine (PostgreSQL, Access, JavaDB, etc.). Note that JavaDB is available with 13 different locales (at the time of writting), so a user wanting JavaDB may want to choose his locale as well. Users may also want to choose the version of their JDBC driver. However this freedom come with an extra cost: the EPSG factories will not work if the user does not put explicitly a JDBC driver on the classpath. As a side-effect, it prevents the user from using the easy syntax:
java -jar geotk-referencing-SNAPSHOT.jar
since the classpath can not be modified that way; he has to use a more verbose command:
java -cp derby-10.4.2.0.jar:geotk-referencing-SNAPSHOT.jar org.geotoolkit.console.ReferencingCommands
A geotk-epsg-javadb module has been added, which has no purpose other than declaring explicitly the dependencies toward Derby. It enables the easier java -jar syntax. This module can also be used during the creation of the Geotk bundles in order to inject the Derby dependencies in the bundles. It would come at the cost of a 2 Mb increase of the JAR file however. This task is about injecting those dependencies, if the increase in download size is considered acceptable.
Issue Links
| Dependency | |||
|---|---|---|---|
|
|
|
||
Added the "JavaDB connection error when stopping Tomcat" issue as depending on this issue because we should make very clear that the JavaDB instance shall be declared in the Tomcat's common/lib directory. Failing to do that cause both the error reported in the linked task, and also a "driver not found" error when undeploying and redeploying an application having an embedded JavaDB JAR. This recommandation could be documented in the geotk-epsg-javadb module.