Bug 76130 - Name validation not consistent
Summary: Name validation not consistent
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: VE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: VE Bugzilla inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-12 17:53 EDT by Richard Kulp CLA
Modified: 2011-06-13 11:38 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Kulp CLA 2004-10-12 17:53:50 EDT
Bean name (field name) validation is not consistent. Create Bean, RenameDialog
(from RenameJavaBeanObjectActionDelegate), and FieldValidator for
NameInMemberComposition (see in JavaVisualEditorPart) each use a different way
to determine if the name is valid.

Some use only the validInstanceVariableRule, some use the rule in combination,
and some just do their own checks. This means some will require a name to be
unique throughout the class, while the other says it must be unique within the
block it is defined in (the class if a field, or the method if it is a local
variable).

They need to be changed to all use the rule, and the rule needs to be changed to
handle local variables.