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 used DB Schema wizard. In the Database Conneciont panel I selected the sample database and the "Please Wait" dialog showed up with progress bar saying "Retrieving the tables". This dialog was modal with no way to cancel it a it looked like it wanted to run indefinitely. I waited 10 minutes. So I had to kill NetBeans. P1 cause there's possible data loss if user sources were not saved. Feel free to downgrade if it's not appropriate.
Additional info: This was in EJB module that was part of Enterprise Application. The location for DB schema was src/conf - selected by default. I tried it again and I can't reproduce it.
Jano, according to Bug priority guidelines (http://qa.netbeans.org/processes/bug_priority_guidelines.html) the issue isn't P1. The bug isn't 100% reproducible. I agree the UI freeze is awkward from user's point of view. Therefore, the right priority is P2.
I guess that the issue was reproduced in NB 5.0 release.
Jano, was the connection to the sample database already connected? Did the "Connect" dialog pop up after selecting the connection in the wizard, asking you to enter a password, or only the "Please Wait" dialog popped up?
I don't remember any dialog prior to the Please Wait dialog when the freeze happend. I would say there that the Connection dialog didn't pop up before. I tried to reproduce it again and there were other dialogs open prior to the Please Wait dialog. The freeze didn't happen in that case.
Could you please try the following: 1. Connect the sample database from the Runtime tab and check "Remember password" in the Connect dialog, 2. Disconnect the sample database. Now try to create a dbschema. You should not get any dialogs except from a Connecting dialog while the database connection is being made, and the Please Wait dialog. Thanks.
I have never reproduced this bug, neither have I seen duplicates for this issue. Hard to tell what happened, because there is no thread dump attached. Closing, please reopen with more details (such as a thread dump) if it occurs again.