How to fix the “No suitable driver found for jdbc:derby” exception?
If you are developing a desktop application with Maven, make sure that your project declares a dependency to the derby artifact from the org.apache.derby group. This is not done automatically by Geotk (except the geotk-epsg-javadb convenience module) because the choice of the database engine (Access, PostgreSQL, etc.) is left to the users. If you are developing a desktop application without Maven, make sure that the derby.jar file is presents on the classpath. If you are developing a server application to be deployed in a container like Glassfish or Tomcat, make sure that the Derby dependency does not appear in the WAR file. This is the opposite of what one may intuitively think. See the geotk-epsg-javadb module for more explanation.
