Description: In your applications, you load the classes either by indirectly referencing them in the code or by directly using java.lang.Class.forName.

# Code your applications

In your applications, you load the classes either by indirectly referencing them in the code or by directly using java.lang.Class.forName.

You load resources the way you normally would, using the standard java.lang.Class.getResourceAsStream, a mechanism that allows an application to access resources defined in the classpath without knowing where or how they are stored.

You do not need to make any changes to the way code interacts with Derby and its JDBC driver. An application can safely attempt to boot Derby, even though it is already running, without any errors. Applications connect to Derby in the usual manner.

Note: The method getResource is not supported.
Parent topic: Class loading overview
Previous topic: Enable database class loading with a property
Related concepts
Dynamic changes to jar files or to the database jar classpath
Signed jar files