isXXX() versus getXXX() for boolean properties

bobx24 · **Joined:** Fri Nov 25, 2005 8:36 am **Posts:** 7

I have a problem with boolean properties.

When I persist a class with AccessType.PROPERTY having a method "boolean isXXX()", then Hibernate persists the XXX boolean field.

So far so good, but if don't wish this field to be persistent or want to annotate it somewhat, I am not able to place an annotation in front of the "isXXX()" method.
However, I can annotate the "boolean getXXX()" method (that is not supposed to exist BTW).

So I end up with two getters per boolean field : the isXXX() for Hibernate, and the getXXX() for annotating the Java code.

This is a little annoying to say the least, does anyone has a clue ? Thanks.

Robert

emmanuel · **Posted:** Wed Dec 14, 2005 12:15 pm

bobx24 wrote:

I am not able to place an annotation in front of the "isXXX()" method.

What do you mean?

bobx24 · **Joined:** Fri Nov 25, 2005 8:36 am **Posts:** 7

I mean for instance that this annotation :

Code:

@Transient boolean isXXX() { return xxx; }

- can't be entered using the JSR220 Eclipse plugin
- if entered manually, is flagged as an error by the Eclipse compiler

Quote:

("Property 'isXXX' is note persistent: Name must follow getXXX pattern")

On the other hand, this one is accepted :

Code:

@Transient boolean getXXX() { return xxx; }

Robert

emmanuel · **Posted:** Wed Dec 14, 2005 1:14 pm

Eclipse JSR-220 is buggy. Hibernate Annotations support @Transient in "is" getters.

max · **Posted:** Wed Dec 14, 2005 2:41 pm

...and you should hopefully be able to enter what you want in the source code.

bobx24 · **Joined:** Fri Nov 25, 2005 8:36 am **Posts:** 7

Well, that's part of my problem : the Eclipse compiler won't compile "@Transient boolean isXXX()" even if it's manually entered.
May be the JSR220-ORM plugin "extended" the compiler in some way.
Robert

emmanuel · **Posted:** Mon Dec 19, 2005 7:33 am

This definitly should work. raise an issue in Eclipse issue tracking.