Hi Ray, > There is a way to eliminate this problem, if this is indeed the cause. > Java application programs, including OO Base, should obviate the default > delegation of class loading by replacing Class.forName() calls with > alternative approaches as illustrated by Ted Neward.
http://www.openoffice.org/issues/show_bug.cgi?id=69624 :) In fact, we plan to change the loading of the HSQLDB driver to use a dedicated class loader, which explicitly looks for the version in the OOo installation (and none else). The original reason was the problem you (and others) reported with different HSQLDB versions, but security, admittedly, is a good additional argument. I'll add your references to the issue. Thanks for following up with this. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
