Affects Version/s: 10.2.1.6
Fix Version/s: None
After setting the derby.database.classpath as a database property the current connection sees its effects, such as being able to load classes from the jar added into the class path. However a newly opened connection does not see its effect. Shutting down and re-booting the database makes the change visible to all.
The new test lang.DatabaseClassLoadingTest will have code that shows this bug commented with this bug number.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Incomplete [ 4 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Workflow||jira [ 12388410 ]||Default workflow, editable Closed status [ 12799847 ]|