subsubprotocol: subsubprotocol,
which is not typically specified, specifies where Derby looks
for a database: in a directory, in a classpath, or in a jar file. It is used
only in rare instances, usually for read-only databases. subsubprotocol is
one of the following:
- directory
- classpath: Databases are treated as read-only databases,
and all databaseNames must begin with at least a slash, because you
specify them "relative" to the classpath directory or archive. (You do not
have to specify classpath as the subsubprotocol; it is implied.)
- jar Databases are treated as read-only databases.
jar: requires an additional element immediately before the
databaseName:
(pathToArchive)
pathToArchive is
the path to the jar or zip file that holds the database and includes the name
of the jar or zip file.
See the Derby Developer's Guide for
examples of database connection URLs for read-only databases.