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.

Bug 74846 - Finalize Entity Classes from Database wizard
Summary: Finalize Entity Classes from Database wizard
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Andrei Badea
URL: http://j2ee.netbeans.org/nonav/docs/p...
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-11 14:29 UTC by jrojcek
Modified: 2006-07-18 22:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jrojcek 2006-04-11 14:29:57 UTC
- there's too big gap betwen the radio buttons and combo boxes. The big gap is also in the next wizard 
step.
- colons are missing in the radio button labels. Should be "Data Source:", not "Data Source".
- "Add Connection" should never be selected in combo box. It is selected when the user cancels the 
"Add Connection" dialog.
- "Generate Named Query Annotations for Persistent Fields" is not in the spec. Either should be added 
to the spec or removed from the implementation.
- all created classes should be selected in project window.
- the persistence unit warning needs to be placed in the panel, not in the inline error bar.
- "Include Related Classes" should be "Include Referenced Classes" according to the spec.
Comment 1 Andrei Badea 2006-04-15 00:24:54 UTC
Re. "Add Connection" should never be selected in combo box: I agree with this.
What should be selected? The last selected connection or nothing? If the last
selected connection, note that selecting a connection causes the wizard to try
to connect to it, which displays the Connect dialog (unless, of course, the
connection is already connected). So the result of the user pressing Cancel in
the New Connection dialog would be a new dialog to popping up...
Comment 2 jrojcek 2006-04-19 17:00:32 UTC
If the connection was already selected, then the wizard was already connected, right? It doesn't need to 
connect again.
Comment 3 Andrei Badea 2006-04-19 19:41:32 UTC
Not necessarily. I suggest to try it out yourself: select a connection, pretend
to realize it's not the one you wanted, so click Cancel in the Connect dialog,
choose New Database Connection from the combo box and click Cancel. The previous
connection is selected and the Connect dialog displayed. 

I'm not sure, maybe this is just a corner case. If you are satisfied with how it
works, I'm ok with it too and let's leave it the way it is, that is select the
previously selected connection when the New Connection dialog is cancelled.
Comment 4 Andrei Badea 2006-07-11 14:48:49 UTC
Updated the UI spec.

Checking in persistence-ui-spec.html;
/cvs/j2ee/www/docs/promog/persistence-ui-spec.html,v  <--  persistence-ui-spec.html
new revision: 1.11; previous revision: 1.10
done
Comment 5 Andrei Badea 2006-07-11 18:02:42 UTC
Fixed. Not possible to select the generated classes in the Projects view, filed
issue 80016 for that.

Checking in
src/org/netbeans/modules/j2ee/persistence/wizard/fromdb/Bundle.properties;
/cvs/j2ee/persistence/src/org/netbeans/modules/j2ee/persistence/wizard/fromdb/Attic/Bundle.properties,v
 <--  Bundle.properties
new revision: 1.1.2.3.2.21; previous revision: 1.1.2.3.2.20
done
Checking in
src/org/netbeans/modules/j2ee/persistence/wizard/fromdb/EntityClassesPanel.form;
/cvs/j2ee/persistence/src/org/netbeans/modules/j2ee/persistence/wizard/fromdb/Attic/EntityClassesPanel.form,v
 <--  EntityClassesPanel.form
new revision: 1.1.2.4; previous revision: 1.1.2.3
done
Checking in
src/org/netbeans/modules/j2ee/persistence/wizard/fromdb/EntityClassesPanel.java;
/cvs/j2ee/persistence/src/org/netbeans/modules/j2ee/persistence/wizard/fromdb/Attic/EntityClassesPanel.java,v
 <--  EntityClassesPanel.java
new revision: 1.1.2.15; previous revision: 1.1.2.14
done
Comment 6 Rochelle Raccah 2006-07-18 22:55:33 UTC
The fix for this causes a regression in the fix for issue 74112.