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 55922 - CMP mapping dialog titles do not follow JLF guidelines
Summary: CMP mapping dialog titles do not follow JLF guidelines
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: All All
: P4 blocker (vote)
Assignee: Rochelle Raccah
URL:
Keywords: UI
Depends on: 55733
Blocks:
  Show dependency tree
 
Reported: 2005-03-03 23:14 UTC by Rochelle Raccah
Modified: 2007-12-10 21:12 UTC (History)
3 users (show)

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 Rochelle Raccah 2005-03-03 23:14:12 UTC
This string is taken from the ejb jar's display
name which is null by default.
Comment 1 Rochelle Raccah 2005-03-22 21:07:37 UTC
I would appreciate HIE input on what it should be.  Now the only way the value
will show null is with an old project, a hand written project, or one where the
user clears out the display name.
Comment 2 Jiri Kopsa 2005-03-23 11:41:39 UTC
Let's make it simple:
Change the title of the "Advanced Settings" dialog (activated from the CMP
Mapping tab of the SJSAS specific logical editor's Entity Bean page) to just
"Advanced Settings - " + ejb-name.

There's no need to include the jar name, since it is activated from the module's
editor.
Comment 3 Rochelle Raccah 2005-03-24 20:47:13 UTC
It turns out that this dialog title doesn't match the JLF guidelines.  The
proposal by HIE is to change it to:
<Bean name> - Advanced Settings
Comment 4 Rochelle Raccah 2005-03-30 01:50:55 UTC
Some other dialogs in the CMP mapping support need this as well, so the total
list is:
1) Map fields to multiple columns
2) Secondary Table setup
3) Secondary Table Editor - maybe
4) Advanced Settings

The structure should be <Bean name> - <Dialog Type>
Comment 5 Rochelle Raccah 2007-08-27 23:06:36 UTC
This issue affects the CMP UI present in the 5.5 config editor, which is not present in 6.0 and is deferred to post 
6.0 (if it ever comes back).
Comment 6 Vince Kraemer 2007-12-08 02:45:24 UTC
if the cmp ui is not coming back... close this issue as will not fix.
Comment 7 Rochelle Raccah 2007-12-10 21:12:12 UTC
CMP UI not present in NB 6.  "cmp" in whiteboard can be used to find these issues if we reenable the CMP UI.