Hello,

I have a Company object which has a many-to-one association to a Contact object (see mapping below). Both are lazily loaded objects. When I attempt to save the Company object, I get the error pasted below that the Contact object is not initialized. However, when I debug and run Hibernate.isInitialized on the the Contact object in the Company object it yields true. Can anyone point me in the right direction of how to fix this? (BTW - I am using Spring but it is just wrapping the actual Hibernate error)

Thanks!

Hibernate version: 2.1.7

Mapping documents: Excerpt from Company object:




Code between sessionFactory.openSession() and session.close(): session.saveOrUpdateCopy(entity);

Full stack trace of any exception that occurs:


Name and version of the database you are using:PostgreSQL 8.0 RC2

Debug level Hibernate log excerpt:

Can someone please help me with this issue? I even explicitly queried the relationship using the fetch keyword and I still get this problem. The issue seems to occur within the Hibernate code itself, since when Hibernate gets the objects and does the dirty check, it is getting the proxy (since the COntact object is lazy).

Thanks,

Rexxe

"org.springframework.dao.InvalidDataAccessApiUsageException: object was an uninitialized proxy for: foo.domain.Contact"

This is not a Hibernate exception, I don't know what it means.

Thanks for replying Christian.

The exception is actually a Hibernate exception wrapped in a Spring exception. Here is the actual Hibernate exception:

net.sf.hibernate.PersistentObjectException: object was an uninitialized proxy for: foo.domain.Contact

Thanks

please try to do this as simple as possible - like with standard hibernate api and see if it works there.

secondkt you dont show code so hard to see what have caused it

I changed the code to use standard hibernate API code and I still get the error. Here is the code I used:



I debugged what was happening in SessionImpl, in particular, in doCopy(Object object, Serializable id, Map copiedAlready) during the cascade.

1. The object starts out as a Contact proxy, but line 4045 of SessionImpl (li.getImplementation()) converts it to its true implementation of a Contact object.

2. Since the Contact object is not new (I'm updating it), it goes to line 4067 where the code gets the result by id and class.

3. Line 4073 of SessionImpl, where the code attempts to unproxy the result from step 2 is where the exception occurs. Since the result loaded in step 2 is a proxy for Contact (since Contact is loaded lazily) and since the get in step 2 does not touch the proxy or uninitialize it, the code is unable to unproxy it which yields the exception. The actual exception occurs at line 996 of SessionImpl in the unproxy method.

It doesn't seem to matter whether I put a proxy or the true implementation of the Contact object in the Company object when I save. The only way I can get this to work is by either making Contact not lazy or by forcing an outer join in the many-to-one mapping of Company to Contact.

Thanks for your help,

Rexxe

ok - you keep showing half the code...where is the code from opening the session to the lines you make ? and where is the exeception ?

...

Max,

The code I provided exists within a Spring web application, so there is a lot of Spring managed things that are done for me. That said, I wrote a JUnit test case that replicates what is happening in the web application. Consequently, I determined where the problem is occuring. What is happening is that because I am using the Open Session In View Filter in singleSession mode, which closes the session after the view is rendered and then reopens upon submission, Spring binds any changes to the object before I have a chance to call session.lock or session.load. As a result, when the object is passed to hibernate's session for saving, the proxy for the contact is not attached to the session and it bombs.

Thanks for your help in this matter,

Rexxe