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.
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.
Created attachment 49851 [details] Java log file
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.
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)
Works now