With Hibernate 3.1, I defined a property as lazily resolved and performed the requisite instrumentation via the Ant InstrumentTask task. While the lazy resolution behaved correctly for objects that I resolved via Session.get(), it did not behave correctly for objects I resolved via Query.list(); cglib failed with a NullPointerException when the proxy attempted to resolve the lazily-loaded property. On a related note, probably, I noticed that Session.get() returned an instance of the target class that referenced the proxy implementation, while Query.list() returns a proxy implementation proper. Please advise.

Thanks.

Actually, the problem is broader than I described: any instance of a class for which you've declared a lazily resolved property and that you've instrumented behaves incorrectly unless you resolve instances of the class with a direct read (e.g., Session.get()). Specifically, while I battled with queries yesterday, it became apparent that instances of the instrumented class behave similarly when those instances are resolved as instance variables in referring classes.