Apache OpenOffice (AOO) Bugzilla – Issue 56548
JDBC + Derby broken: The specified driver could not be loaded!
Last modified: 2006-06-12 15:53:42 UTC
Hi, Please note, I suspect this to be the smae manefestation as issue 56454, but was unsure whether to raise this as a new bug or simply comments on 56454. IMPORTANT: I fell back to OOo 2.0 beta 2, and with no change to any settings JDBC access to derby worked first time. ----8<--- The Error from Base -------- When trying to access mysql database with JDBC access I receive this error: Error code: 1000 The specified driver could not be loaded! Error code: -1 org.apache.derby.jdbc.ClientDriver -----8<---------------- I have you read the dba FAQ: http://dba.openoffice.org/FAQ/index.html#jdbcdriver And have also checked the file: ./user/config/javasettings_Windows_x86.xml ... Here it is, the jar files are in the paths specified: <?xml version="1.0" encoding="UTF-8"?> <!--This is a generated file. Do not alter this file!--> <java xmlns="http://openoffice.org/2004/java/framework/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <enabled xsi:nil="true"/> <userClassPath xsi:nil="false">C:\derby\lib\derbyclient.jar</userClassPath> <vmParameters xsi:nil="false"/> <jreLocations xsi:nil="true"/> <javaInfo xsi:nil="false" vendorUpdate="2004-01-30" autoSelect="false"> <vendor>Sun Microsystems Inc.</vendor> <location>file:///C:/jdk1.5.0_01/jre</location> <version>1.5.0_01</version> <features>0</features> <requirements>0</requirements> <vendorData>660069006C0065003A002F002F002F0043003A002F006A0064006B0031002E0035002E0030005F00300031002F006A00720065002F00620069006E002F0063006C00690065006E0074002F006A0076006D002E0064006C006C00</vendorData> </javaInfo> </java>
Oops cut&paste :$ Should read: ... ----8<--- The Error from Base -------- When trying to access derby database with JDBC access I receive this error: ...
Hi, I have no problem load this driver. I have used db-derby-10.1.2.1-bin and insert derbyclient.jar to my staroffice classpath. The I can load the class org.apache.derby.jdbc.ClientDriver Can you please hava again a look on this issue? Bye Marc
not repro & no respond => close do not hestitate to reopen this issue if bug is still reproducable in current version thx