Certain conditions must be met for Derby to be able to load the new
classes right away without you having to reboot:
- You originally configured database-level class
loading for the database correctly. Turning on the database-level class loading
property requires setting the derby.database.classpath property with valid two-part names, then rebooting.
- If changes to the derby.database.classpath property
are needed to reflect new jar files, you change the property to a valid value.
If these requirements are not met, you will have to reboot to see the changes.