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 69870 - Calling a DerbyOptions method causes the Derby drivers to be registered
Summary: Calling a DerbyOptions method causes the Derby drivers to be registered
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2005-12-05 10:57 UTC by Andrei Badea
Modified: 2005-12-05 15:35 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 Andrei Badea 2005-12-05 10:57:04 UTC 
When a DerbyOptions method is called *for the first time* the Derby drivers are
registered. This is caused by the SystemOption initialization calling the
property setter methods of its superclass. Thus the setLocation() method is
called when DerbyOptions is initialized, and setLocation() causes the Derby
drivers to be registered.
Comment 1 Andrei Badea 2005-12-05 11:00:22 UTC 
Causes the initialization of the Database Explorer on every startup of an IDE
with a registered appserver instance.
Comment 2 Andrei Badea 2005-12-05 15:35:21 UTC 
Fixed.

Checking in src/org/netbeans/modules/derby/DerbyOptions.java;
/cvs/db/derby/src/org/netbeans/modules/derby/DerbyOptions.java,v  <-- 
DerbyOptions.java
new revision: 1.6; previous revision: 1.5
done