All,

I just noticed that the laziness of a persistent class is tied to the class mapping, not to the association. I can't find much discussion about how this came to be, but it seems to me that one might want the lazy-load attribute on a per-association basis, not a per class basis. Is there a way to control this?

-Chris

Both classes and associations can be lazy.

There is nothing documented for one-to-one or many-to-one that appears to specify the laziness. Can you explain?

Thanks for the reply, but maybe I wasn't specific enough. I'm talking about one-to-one associations. The kind that generate a CGLIB proxy at runtime. In some cases this may also be a many-to-one, if you aren't doing the association via a shared foreign key. In any case, I'm not talking about collections.

-Chris

perhaps fetch="select"

That looks to be an option only in H3, and then it seems to pertain only to subclass/inheritance stuff, but I could be wrong here.

I'd like to have a lazy reference to some class in one place, yet have a direct reference to the same class in another place. Anyone know the answer to this beyond speculation?

-Chris

H3 has the many-to-one lasy load option but its a field level lazy load attribute meaning it requires build time enhancement. Personally, class level lazy loading works very well and its easy enough to force the proxy to load the object when required.