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 117193 - Unable to link Oracle table to table component
Summary: Unable to link Oracle table to table component
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: John Baker
URL:
Keywords:
Depends on: 87600
Blocks:
  Show dependency tree
 
Reported: 2007-10-01 04:52 UTC by br_esper
Modified: 2007-11-02 06:21 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Java log file (33.86 KB, application/octet-stream)
2007-10-01 04:54 UTC, br_esper
Details

Note You need to log in before you can comment on or make changes to this bug.
Description br_esper 2007-10-01 04:52:56 UTC
I am trying to attach an Oracle table to a table component and recieve the following dialog:

A java.lang.UnsatisfiedLinkError exception has occurred.
Please report this at http://www.netbeans.org/community/issues.html,
including a copy of your messages.log file as an attachment.
The messages.log file is located in your C:\Documents and Settings\tcrowl\.netbeans\5.5.1\var\log folder.
Comment 1 br_esper 2007-10-01 04:54:19 UTC
Created attachment 49851 [details]
Java log file
Comment 2 Andrei Badea 2007-10-02 12:57:49 UTC
Not clear which class loader has already loaded the native library. It might be a driver class loader in the DB
Explorer, or perhaps a class loader created by the visual web database support. Anyway, visual web should not make its
own connections, but use the DB Explorer for that.
Comment 3 John Baker 2007-10-04 00:57:14 UTC
The problem is VW does rely on the driver to get a connection, not DB Explorer.

One of the reasons to not use DB Explorer is the user would have to enter a password
everytime a page is opened (if the connection is not open) and as a result, the 
ugly Component Error page opens.

The other reason is the implementation of VW's CachedRowSetDataProvider which requires
a live connection. 

So, there would have to be 2 changes:
1) Password saving implemented 87600
2) CachedRowSet changes

I'll see if this can be fixed for 6.0 (probably not beta2)

Comment 4 John Baker 2007-11-02 06:21:54 UTC
Works now