I'm not sure if I understood the lazy thing in hibernate.

My idea is like this that i can find my orders from primary Table and send it to the view in a searchresult List.

The user decides which order he want's to see. At this time I want to load the whole order with it's childrens. For example a SupplierId.

In the searchresult i only want to see the supplierId while in the detail view i'd like to see the supplier details got by the supplier table.

mapping between order and supplier is many to one. One order can have o supplier. A supplier can be in many orders.

My Idea was that there is something like loadLazy and LoadFull.

Any Answer is welcome!

Thanks, Christian


P.S. Not Using the ViewSession Pattern...

Typically Lazy initialization would be helpful in a many-to-one,one-to-many bi-directional relation.

To take your example, you have 3 entities here:

User
Order
Supplier

User and Order share a 1-to-many relation
Order and Supplier share a 1-1 relation

Let's say that a user want's to look at all his orders, you do a load on the User (with the userid or some selection criteria).

You User Object would have a collection that would represent the Orders that the user has.

In your Hibernate mapping say we define something like this:



When you do a session.load() or find(), the user object's collection would be populated only with Proxies to the UserOrder object and would not load the properties of the UserOrder.

Once you select the order, you selectively load the UserOrder from the collection using the collection's accessor methods, at this point, it would load and populate the properties of the UserOrder entity that you are trying to show to the user.

The supplier as part of the Order would also work in a similar fashion.

You can set the "hibernate.show_sql" property to "true" to find the difference.

Hope that helps. I am also a beginner to Hibernate and hoping that a more advanced user would give me a better explanation.

-Anand

Ah ok. And this works also if I load the second part in a different Session?

Like the example i've written above. First comes a searchresult of orders with lazy initialization. This happens in one session and gets rendered through html to the client.

In the second session when the user selected which order he wants, then i pull out the order of the collection and its completly initialized?

You need to reattach the first object to achieve that in a different session

Ah thanks... now I found the page http://www.hibernate.org/hib_docs/refer ... pdate-lock
in the documentation. I'll try this out. further questions may follow ;-)