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 81163 - It is not possible to add additional validation of target name in JavaTargetChooserPanel
Summary: It is not possible to add additional validation of target name in JavaTargetC...
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords: API
Depends on:
Blocks: 80720
  Show dependency tree
 
Reported: 2006-07-26 14:12 UTC by Martin Adamek
Modified: 2008-11-05 12:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Proposed patch (892 bytes, text/plain)
2006-07-26 14:13 UTC, Martin Adamek 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Adamek 2006-07-26 14:12:57 UTC 
We need to add some additional validation to class name field (e.g. it cannot be
reserver SQL keyword for Entity class wizard). I propose simple solution: call
Templates.setTargetName() in isValid() method of this panel. Currently it is
called in storeSettings(), so it means it is not possible to get target name
before panel is finished.
Comment 1 Martin Adamek 2006-07-26 14:13:32 UTC 
Created attachment 32230 [details]
Proposed patch
Comment 2 martin_adamek 2007-06-25 08:09:04 UTC 
Is there any plan to do this for 6.0? We really need it also in other use cases, e.g. generation of multiple classes
(Session EJB) and checking if inserted name + prefix and suffix is already taken.
Comment 3 Andrei Badea 2007-06-25 11:37:20 UTC 
This has been set to future since 5.5, setting back to TBD.
Comment 4 martin_adamek 2007-08-01 14:07:47 UTC 
Forget the patch, it is useless (doesn't consider package, for example). I have my own version of this, may come with some enhancements and API change in 
future after I will collect more use-cases.
Comment 5 Marian Mirilovic 2008-11-05 12:09:03 UTC 
incorrect resolution LATER->WORKSFORME
Comment 6 Marian Mirilovic 2008-11-05 12:10:27 UTC 
.