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.
When asking NetBeans to generate getters for a boolean field foo, it kindly creates a method isFoo(). But if we want a getter for the Boolean class, then the getter is named getFoo(). I expected the getter generator to make a isFoo() method for both boolean and Boolean types.
Sounds reasonable to me.
Fixed. --- http://hg.netbeans.org/jet-main/rev/bac1f4b232bf
Integrated into 'main-golden', will be available in build *200903281400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/bac1f4b232bf User: Max Sauer <msauer@netbeans.org> Log: #160531: Generate is-like setter for java.lang.Boolean
I am really reading this or I am getting an nightmare? How could this possible, generate isXXX for java.lang.Boolean? It is totally against JavaBean specification. Just primitive boolean must be isXXX and this fix generated several regressions such as: . For editor, the getter never exists since isXXX for Boolean is not valid (getter generation is always visible); . Encapsulate fields (thanks God) don't work like this; So, now we have an inconsistent IDE that makes users looks crazy when using facing wrong behaviours from tools that believe in JavaBean spec like Hibernate, Swing palette components at NetBeans and several others, since we trust in what IDE generates. The issue #168061 was created about that and I agree with Jan Lahoda, this patch _must_ be reverted since similar with patch suggested and make available as soon as possible. I will reopen it and wait for you revert it asap and mark this as WONTFIX. I just can't believe in that yet...
Reverted this one and marking as WONTFIX, since it does not follow JavaBeans spec. --- http://hg.netbeans.org/jet-main/rev/a361b3bc8ec8