Issue 77730 - JBDC connection to HSQL file based database fails
Summary: JBDC connection to HSQL file based database fails
Status: CLOSED WONT_FIX
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m212
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2007-05-23 20:39 UTC by drewjensen.inbox
Modified: 2013-08-07 15:45 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description drewjensen.inbox 2007-05-23 20:39:03 UTC
To Recreate
Download the files attached to Issue 17830
Follow steps outlined in that issue to connect to file based database.
Open Base file and click on Tables.
Error 'The connection to the datasource...can not be established'
Look at the extended information and the error is:
"The specified driver could not be loaded!"

This does work with 2.2.1 RC2. 

If you go to Options>Java and explicitly add the hsqldb.jar file, from HSQLdb
into the classpath you can open the database. This was not necessary with 2.2.1
Comment 1 drewjensen.inbox 2007-05-23 20:39:22 UTC
.
Comment 2 drewjensen.inbox 2007-05-23 20:41:19 UTC
Sorry, the files and steps are in ISSUE 71830
Comment 3 Frank Schönheit 2007-06-11 11:35:40 UTC
With some recent milestone (not sure which one), the behaviour of OOo was
changed so that it does *not* automatically add all files in the program/classes
folder to Java's class path, when starting the JVM. Instead, classes are loaded
with dedicated class loaders on demand only.

This change has been done for performance reasons, since this noticeably speeds
up the start of the JVM, and the start of Java components (since now not all the
JARs in the classes folder need to be searched for given classes).

That said, this issue here is a side-effect which cannot be fixed without
re-introducing performance problems - which it is not worth, IMO. That's why
closing as WONTFIX - finally, there is the workaround of manually adding the
file to the CLASSPATH in Tools/Options/Java.

(Side note: If "external HSQL databases" are something we want to make more
easily accessible, this should probably be done by introducing a respective type
in the File/New/Database wizard, similar to the "Oracle JDBC" type ...)
Comment 4 christoph.lukasiak 2007-06-12 11:34:02 UTC
close