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: | [60cat] cant deploy web application while ide has db connection created for postgresql | ||
---|---|---|---|
Product: | serverplugins | Reporter: | pbelbin <pbelbin> |
Component: | Sun Appserver 9 | Assignee: | Nitya Doraisamy <nityad> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | jbaker |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | Other | ||
OS: | Other | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
pbelbin
2007-10-26 16:43:27 UTC
There was a bug in serverplugins that unfortunately was fixed after beta2. http://www.netbeans.org/issues/show_bug.cgi?id=119278 To restore the database connection, right-click on the project and choose Resolve Database Problem. The dialog will help restore the database connection. To workaround the "Checking for missing JDBC drivers..." you could try copying the Postgres driver to the Glassfish installation lib directory. To see the installation directory of Glassfish from the Services window, select the node representing Glassfish and view the Properties This was fixed in trunk (119278) and is fixed in the daily builds. But did not make it into beta2. To workaround, you can disable JDBC Driver deployment at Services->GlassFish V2->Properties->Options->JDBC Driver(s) Deployment Enabled. You will be able to have the database connections in the IDE. But the plugin will not try to copy the driver jars. You will manually need to place it in the server's classpath. *** This issue has been marked as a duplicate of 119278 *** thank you for all the help in making the connection with the other issue that's already been resolved, and, how to work around the issue in the beta2 release. keep up the good work people! The workaround that nityad suggests in this issue did not work for me (NB6b2) deployment still hangs and the message still appears "Checking for missing JDBC drivers ..." ? Maybe restarting NetBeans Restarting NB6b2 did not help matters. I tried reporting the exception that netbeans caught, but the website recognized it as belonging to this closed issue and ignored it. :-/ Confirmed that suggested workaround disabling "JDBC Driver(s)Deployment Enabled" is still causing the driver jar copy to be aatempted. Filed issue http://www.netbeans.org/issues/show_bug.cgi?id=120731 |