https://bugs.documentfoundation.org/show_bug.cgi?id=34411
--- Comment #25 from prrv...@gmail.com --- Hi all, I would like to express my opinion in this conversation. I am not a Java specialist but its use has led me to notice several things: - Once a JDBC driver is loaded, regardless of how it is loaded, you will only be able to use this version of the driver until LibreOffice is closed (the Java engine stops). - There are at least 2 ways to load a JDBC driver. - By putting the driver in the Java classPath. But putting the jar archive in the ClassPath prevents any use of a URL Class Loader on this archive since when using a URL Class Loader, Java will look to load first by scanning the Java ClassPath then if it doesn't find it will use the URL Class Loader. - Using a URL class loader allowing you to fetch the correct version using the URL pointing to this version. Under Linux if you install the components in LibreOffice allowing you to use HsqlDB in integrated mode then the HsqlDB 1.8 jar archive will be put in the Java ClassPath (this will prevent any use other than version 1.8). This is not true for the installation of LibreOffice under Windows... It is apparently a Java URL Class loader which is used. I think that these limitations are immutable, we cannot do without taking them into account. -- You are receiving this mail because: You are the assignee for the bug.
