Hibernate version: 3.1.2

We are upgrading from Hib2 to Hib3 and have run into an issue when calling Hibernate.initialize. In this case our entity does not exist in the database but because we are lazy loading the session.load() still returns a proxy. The first call to initialize() throws an ObjectNotFoundException as expected. The second call however does not throw the ObjectNotFoundException even though the entity still doesn't exist.

While debugging through AbstractLazyInitializer.initialize() I found the first call sets an initialized flag, prior to throwing the ObjectNotFoundException. The second call sees the initialized flag is set which prevents the immediateLoad, and therefore prevents the ObjectNotFoundException on the second call.

We can work around this problem by evicting the proxy from the session after the first ObjectNotFoundException, but is this functioning as designed or bug that needs reporting?

From section 10.3 of the Hibernate 3.2.3 manual:



get() will give you null if the row doesn't exist. You can check for that and handle appropriately.

-Chris