Persistence problems for methods which start with get or is

radus · **Joined:** Tue Mar 28, 2006 3:08 pm **Posts:** 2

Hi,

In one of my entity classes I have defined these 2 methods:
public String getFirstName(){
return "";
}

public boolean isManager(){
return true;
}

I don't have the setter methods (setFirstName(..) and setManager(..)) nor the fields (String firstName; and boolean manager;) defined in my class.
Anyway when the class is persisted two columns are created in the database(FIRSTNAME and MANAGER).
What does this mean? That I have to annotate with @Transient every method which starts with get or is and I don't want to be persisted?
I think this is a bug.

I'm using: hibernate-3.2.0.cr1, hibernate-annotations-3.1beta9, hibernate-entitymanager-3.1beta7, hibernate-tools-3.1.0beta4 and ejb3-persistence(all of these built today from the SVN repository).

Thanks.

jt_1000 · **Posted:** Tue Mar 28, 2006 6:23 pm

(I edited my response). I made the comment, and I realized you are using annotations... sorry, can't comment.

jt_1000 · **Posted:** Tue Mar 28, 2006 6:29 pm

Yet, I did managed to find this out of the docs:

Quote:

Every non static non transient property (field or method) of an entity bean is considered persistent, unless you
annotate it as @Transient. Not having an annotation for your property is equivalent to the appropriate @Basic
annotation. The @Basic annotation allows you to declare the fetching strategy for a property:

page 4 of
http://www.hibernate.org/hib_docs/annotations/reference/en/pdf/hibernate_annotations.pdf

Hope it helps!

radus · **Joined:** Tue Mar 28, 2006 3:08 pm **Posts:** 2

Actually, the EJB3 Proposed Final Draft spec (sec. 2.1.1) states that:

Quote:

It is required that the entity class follow the method conventions for a JavaBean when persistent properties
are used.
In this case, for every persistent property property of type T of the entity, there is a getter method, get-
Property, and setter method setProperty. For boolean properties, isProperty is an alternative name for
the getter method.

In other words, in order for a bean to define a property, both setter and getter must be defined. It's not enough that only a get*() or is*() method exists.

Is this a case of Hibernate "relaxing" the definition of JavaBean property? If so, it should be made very clear as I'm sure lots of people would run into this issue.

It could also be that this interpretation of JavaBeans properties is used just while creating a schema from annotated classes, although I believe that the same metamodel is used at runtime too.

jt_1000 · **Posted:** Tue Mar 28, 2006 7:32 pm

what you say makes sense - I think we concluded that you did in fact need to put transient as an annotation.

emmanuel · **Posted:** Sat Apr 01, 2006 12:09 pm

radus wrote:

That I have to annotate with @Transient every method which starts with get or is and I don't want to be persisted?

Correct