Lazy loading feature

vrnroman · **Joined:** Thu Jun 09, 2011 1:59 am **Posts:** 3

Hello.
I want to use Lazy loading, so I have next entitys:

Code:

class BigEntity {
  @ManyToOne(fetch = LAZY)
  @LazyToOne(NO_PROXY)
  private InnerEntity inner;
}

I want to get the next behavior:

Code:

BigEntity big = em.find(BigEntity.class, id);

hibernate: select * from BigEntity where id = ?

Code:

InnerEntity inner = big.getInner();

hibernate: select * from InnerEntity where id = ?

But I have next situation:
select * from InnerEntity where id = ? send to DB when I get some property of InnerEntity, but not when I call big.getInner();

mmerder · **Posted:** Thu Jun 09, 2011 3:39 am

So what is your problem. This is lazy loading... As soon as you want to get information about innerEntity it has to be fetched.

vrnroman · **Joined:** Thu Jun 09, 2011 1:59 am **Posts:** 3

Thank you for replay/

I want hibernate to send select request, when I call

Code:

big.getInner()

but not when I call

Code:

big.getInner().getField()

davispw · **Joined:** Wed Jun 01, 2011 1:16 am **Posts:** 4

vrnroman wrote:

I want hibernate to send select request, when I call

Code:

big.getInner()

When you call

Code:

big.getInner()

you will get a proxy that is not initialized until you force it.

You could call

Code:

Hibernate.initialize(big.getInner())

to load whenever you want. Does that help?

http://docs.jboss.org/hibernate/core/3. ... ialization

What you're asking for specifically is called "no-proxy" fetching (see here: http://docs.jboss.org/hibernate/core/3. ... e-fetching). It requires bytecode implementation so you can say whether it is worth the trouble.

vrnroman · **Joined:** Thu Jun 09, 2011 1:59 am **Posts:** 3

Yes, you are right, initialing "by-hand" helps me:

Code:

Hibernate.initialize(big.getInner())

I think this solution "smells": there are too many places for this static method in project. But, as I see, no_proxy mechanism is deprecated. So I choose static method.

Thank you