This property, which behaves like a classpath, specifies the jar files
to be searched for classes and resources and the order in which they are searched.
If does not find
a needed class stored in the database, it can retrieve the class from the
user's classpath. ( first
looks in the user's classpath before looking in the database.)
- Separate jar files with a colon (:).
- Use fully qualified identifiers for the jar files (schema name and jar
name).
- Set the property as a database-level property for the database.
Example:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.database.classpath',
'APP.ToursLogic:APP.ACCOUNTINGLOGIC')
See "derby.database.classpath" in the
for more information about the
property.
's class loader
looks first in the user's classpath for any needed classes, and then in the
database. To ensure class loading with the database class loader, remove classes
from the classpath.