If you have an IDE or a DB tool, you cannot dynamically load/unload the embedded derby driver.
In Eclipse BIRT, this created the following situation: The examples use Derby 10.1. My application uses 10.2. I can't switch between the examples and the reports in my application without restarting Eclipse and patching the Derby plugin.
It would be great if you could add a method which we could call to cleanup the embedded driver so we can throw the classloader away and load another instance of Derby.