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.
| Summary: | Unable to link Oracle table to table component | ||
|---|---|---|---|
| Product: | obsolete | Reporter: | br_esper <br_esper> |
| Component: | visualweb | Assignee: | John Baker <jbaker> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | abadea, davidvc |
| Priority: | P3 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 87600 | ||
| Bug Blocks: | |||
| Attachments: | Java log file | ||
|
Description
br_esper
2007-10-01 04:52:56 UTC
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 |