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 152037 - oracle drivers keep multiplying in the new connection dialog
Summary: oracle drivers keep multiplying in the new connection dialog
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks: 152580
  Show dependency tree
 
Reported: 2008-10-31 19:34 UTC by ats37
Modified: 2010-01-06 03:38 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (48.99 KB, image/png)
2008-10-31 19:36 UTC, ats37
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ats37 2008-10-31 19:34:57 UTC
I just installed the 6.5 RC2 (JDK 1.6.0_02 on Windows XP) and set about configuring the various database connections I'd
had in the earlier beta.

Under Services->Databases->Drivers I added entries for Sybase jConnect 5.5 (jconn2.jar) and the Oracle Thin versions
11.1 (ojdbc6.jar & ora18n.jar) and 9.2.0 (ojdbc14.jar & nls_charset12.jar).  Then I started adding the jConnect
connections for our various Sybase databases.

After doing a couple of them, I realised while doing the next one that the Name dropdown up the top of the New
Connection dialog was getting longer - after the three Oracle v11.1 entries that had "with Service ID(SID)", "with
Service Name" & "with TNS Name ..." on the end, there were half a dozen entries with just "Oracle (v11.1)".  After
those, were several more "Oracle (v9.2.0)" ones before I got to the Postfix and Sybase entries (none of which, I
noticed, had any mention of Service Name etc.).  I finished adding the connection and started the next one - the number
of Oracle entries in the list had grown further.  This was the same whichever of the radio buttons (Field Entry or
Direct URL Entry) I selected.
In all this, it was Sybase jConnect connections that I was adding, I hadn't started on any of my Oracle ones yet.  But
is seems that with each one I did, more Oracle entries were being added to this drop down.  I haven't actually tried
adding an Oracle connection to see what that does.  Throughout, the Drivers folder in the treeview still only showed the
one entry for each driver.

I'll upload a screenshot.

I can't remember exactly when I set up the various drivers in the older NB version; I suspect the Oracle ones were a
later addition so I probably wouldn't have seen this before anyway.
Comment 1 ats37 2008-10-31 19:36:36 UTC
Created attachment 73019 [details]
screenshot
Comment 2 David Vancouvering 2008-10-31 19:43:01 UTC
I thought we fixed this.  See issue 149492.  It was fixed on Oct 9 and I see the change set in the release65 branch:
http://hg.netbeans.org/release65/rev/9fde0e84ba5a

So it's disconcerting that it's still there.  ats37: can you get the latest build at
http://bits.netbeans.org/nightly/latest and see if you can reproduce there?
Comment 3 ats37 2008-10-31 20:02:32 UTC
I'm not sure it's exactly the same problem as #149492; I'm not getting extra entries for all the drivers, only for Oracle.
And of course it's only for Oracle that I've got two drivers configured, both of which have oracle.jdbc.OracleDriver set
as the driver class...

If I have time later this evening, though, I'll download the latest nightly and see if that does the same.

I notice that the properties page for the existing Oracle connections (in NB6.5beta) don't actually display the driver
name with version number that I entered, just the driver classname.  Am I right in thinking it's a matter of luck (or
perhaps alphabetical, or down to the order they register with the DriverManager) which jars will actually be used when I
open that connection?
Comment 4 David Vancouvering 2008-10-31 20:53:34 UTC
OK, this does sound like a different bug.  We'll take a look at it.
Comment 5 Jiri Rechtacek 2009-02-10 15:26:33 UTC
Reassigned to new owner.
Comment 6 Jiri Rechtacek 2009-12-02 08:32:01 UTC
It's still a valid issue?
Comment 7 Jiri Rechtacek 2010-01-06 03:38:27 UTC
No response from the reporter for a long time, closed as WFM.