Hm..can't find in DTD and documentataion: can Components can be load-on-demand?

I have entity object, which have one property - text, mapped to CLOB, and the size of this text can be rather big (about 1Mb for instance)

I have 2 web-pages:
1 - displays my entities info, without that text.
2 - displays detailed info about entity.

So, i wonder can i use some kind of lazy-load for this property, because now
it's become a perfomance problem. Hibernate queries all this CLOB text, and it slowwww ;(

Your help is very appreciated.

Use lightweight class pattern (in the Wiki) or use a real sql.Clob as class property, which is lazy by nature.

Hum we should write some materials on that in the wiki area.

I have this same issue. I have a large byte[] as a property of a dependent component (i.e. it's not an entity so I can't split it up as a different class). I just want that one property to be lazy loaded, not all the others.

Is it really true that the only way to accomplish this is by modifying your class structure?

I'm still trying to discover the elegance everyone says about Hibernate. Every time I need to do something that's more than a simple case, I find Hibernate to largely intrude on my design and require custom code for mappings.

Is is true that we prefer the use of projection rather that property-level lazy fetching, and it is the reason why it is not /yet/ impelmented in Hibernate.
So, you don't strictly have to modify your domaion model. What other domain model modification you had to do?

Alright, alright we will add bloody lazy property fetching.

Your code will be slow but "elegant". All those "elegant" n+1 selects that make your DBA so happy...

I am sick of trying to teach people how to use projection.