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: | ClassNotFoundException with iReport plugin Again | ||
---|---|---|---|
Product: | updatecenters | Reporter: | pekinsoft <pekinsoft> |
Component: | Pluginportal | Assignee: | pekinsoft <pekinsoft> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
URL: | http://www.pekinsoft.net/bugs/JDBC-stacktrace.html | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Test Application's Database Server Settings
Test Application Running...Connected to database with record showing. Settings in Database JDBC Connection Dialog...Notice that they match my test application's settings. Results of clicking on the Test button. |
Description
pekinsoft
2008-05-02 04:33:46 UTC
Created attachment 60944 [details]
Test Application's Database Server Settings
Created attachment 60945 [details]
Test Application Running...Connected to database with record showing.
Created attachment 60946 [details]
Settings in Database JDBC Connection Dialog...Notice that they match my test application's settings.
Created attachment 60947 [details]
Results of clicking on the Test button.
As you can see in the attached screenshots, I matched the settings in the Database JDBC Connection Settings dialog box with those for the connection that I already had established in the test application. This seems to be a redundant thing to have to do, but I have jumped through these hoops. After doing so, even though the connection works fine in the application, the iReport plug-in continues to fail. I had tried the database URL, both, with and without the port number (3306). No matter what I try, I continue to get the ClassNotFoundException on the org.mysql.jdbc.Driver class. Giulio, it looks like the fix didn't help. Do you have any other idea what might cause this? Sean, are you 100% sure you didn't use the previous version of the plugin? The plugin did not get updated properly. This is a plugin portal problem and not the iReport plugin problem. For some reason the plugin will not upload. OK I just got the plugin to upload manually. Please retry. OK, Sean can you please double test the problem again with the new version? Thanks! I think it's fixed now. Yes, the plug-in is fixed and working as expected now. iReport is good to go. Thanks, Giulio, for your prompt fix. Cheers, Sean Carrick |