This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 195496 - Derby driver and sample connection not registered by default
Summary: Derby driver and sample connection not registered by default
Status: VERIFIED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 7.0
Hardware: PC Linux
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on: 195498
Blocks:
  Show dependency tree
 
Reported: 2011-02-15 10:18 UTC by Petr Jiricka
Modified: 2011-02-16 08:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2011-02-15 10:18:06 UTC 
Ubuntu 10.10.

1. Installed sun-java6-javadb using the Synaptic Package Manager
2. Started the IDE

I would expect that the JavaDB driver + sample connection will be pre-registered in the IDE, but they are not. The driver is located under /usr/lib/jvm/java-6-sun/db/lib.
Comment 1 Jiri Rechtacek 2011-02-15 11:02:53 UTC 
Petr, did you install IDE via installer or simply unzip a archive?
Comment 2 Petr Jiricka 2011-02-15 11:09:06 UTC 
Just unzipped the build (beta 2 candidate build). 

I know that on Mac, when I use the zip build, Derby registration works well. Not sure about Windows.
Comment 3 Jiri Rechtacek 2011-02-15 11:38:09 UTC 
I'll look in it.
Comment 4 Jiri Rechtacek 2011-02-15 19:38:49 UTC 
It works for me, if you run IDE with appropriate java ie. --jdkhome /usr/lib/jvm/java-6-sun in this case, the derby location in /usr/lib/jvm/java-6-sun/db/lib is detected. The current logic of derby locator finds derby on <jdkhome>/db/lib, depends on active java home in IDE. If you think it's good to explore all known places where derby could found, reopen it again.
Comment 5 Petr Jiricka 2011-02-16 08:17:09 UTC 
Ok, I agree the current logic sounds reasonable. When I specify --jdkhome explicitly, the IDE correctly picks up the JavaDB location and registers the driver + sample database. 
The root problem then is bug 195498, i.e. the IDE launcher should respect the OS default, so I don't need to explicitly specify --jdkhome.