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: | Can not get out of the New JDBC Driver dialog | ||
|---|---|---|---|
| Product: | javaee | Reporter: | Dongmei Cao <dongmeic> |
| Component: | Hibernate | Assignee: | Vadiraj Deshpande <vadirajvd> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | ||
| Priority: | P2 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 129633 | ||
| Bug Blocks: | |||
| Attachments: | Sample project to reproduce the bug | ||
Created attachment 59262 [details]
Sample project to reproduce the bug
I agree that this is an issue specially the JDBC driver dialog. If the driver is not found in the XML, this dialog pops up to ask the driver information from the user. This is same behavior as with db api. When the dialog is shown, user have the option of specifying the driver details, and upon providing the details, the connection is established and CC will be activated. Investigating further. This issue is because the Database Explorer API do not have any feedback from the Add Driver dialog. See http://www.netbeans.org/issues/show_bug.cgi?id=129633 The issue with add driver dialog showing in never ending loop is fixed. The user feedback messages will be handled in separate enhancement. (http://www.netbeans.org/issues/show_bug.cgi?id=131722) Verified Product Version: NetBeans IDE Dev (Build 200811240201) Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15 System: Linux version 2.6.27-7-generic running on i386; UTF-8; en_US (nb) |
Use the attached project and try to CC on the table attribute in the Trip.hbm.xml. It pops up the New JDBC Driver dialog. But there is no way to get out of this dialog. I have to kill the IDE by Ctrl-C. The cause is from the configuration file. Notice I have commented out <!-- comment them out to reproduce the bug <property name="hibernate.connection.driver_class">org.apache.derby.jdbc.ClientDriver</property> <property name="hibernate.connection.url">jdbc:derby://localhost:1527/travel</property> --> If there is no driver_class specified in the configuration file, the New JDBC Driver dialog will pop up and get stuck. If the driver_class is specified and no url is specified, then CC gives "No Suggestion", which is expected.