I'm in the process of converting a JDBC database layer to Hibernate, and many of the POJOs have public members. I've come across a strange issue with this, however.

I have a POJO similar to the one below:

public class pojo
{
@Id
public int id;

@Column(name="member")
public String member;

public String getMember()
{
return member;
}
}

if i call pojo.member, I get a null, however, if I call pojo.getMember() then it succeeds... Is there a reason for this?

When you first retrieve an entity it may only be populated with the Id.

When you make a call to access a property Hibernate will go off to get the rest of the details.

If you output the type of the POJO you may find that it is actually a proxy.


--
Stephen Souness

I didn't actually realize that the entire object is lazy loaded. I figured it was just for collections.

Is there any way to specify the fetch type globally, or is it always lazy?

By default, we have lazy=true but we can set this globally also, like below:

Example:

<hibernate-mapping
schema="AUCTION"
default-lazy="false"
default-access="field"
auto-import="false">
<class ...>
...
</class>
</hibernate-mapping>