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 202290 - [71cat] optimized encapsulate fields
Summary: [71cat] optimized encapsulate fields
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Jan Becicka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-19 09:09 UTC by muellermi
Modified: 2011-11-16 16:39 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 muellermi 2011-09-19 09:09:19 UTC 
Product Version = NetBeans IDE Dev (Build 201109180600)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.7.0
Runtime = Java HotSpot(TM) Client VM 21.0-b17

let's assume there is an attribute like this
private boolean _isComplete;

encapsulate field will generate an ugly pair for getter/setter
    public boolean isIsComplete() {
    public void setIsComplete(boolean isComplete) {

--> if an attribute starts with "_is" or "is" don't keep this / don't double "is"
suggested generated getter/setter
    public boolean isComplete() {
    public void setComplete(boolean isComplete) {
Comment 1 Ralph Ruijs 2011-09-20 11:37:41 UTC 
I think the current behavior is correct. The spec states:
get<PropertyName>()
or as an alternative for booleans
is<PropertyName>()

Marking as wontfix.