I'm using jdk1.3.1_09 with Hibernate 2.1.2.

I'm adding a child object to a collection that has lazy="true" and I get:

20:36:01,812 ERROR LazyInitializationException:? - Failed to lazily initialize a collection - no session or session was closed

net.sf.hibernate.LazyInitializationException: Failed to lazily initialize a collection - no session or session was closed

void net.sf.hibernate.collection.PersistentCollection.initialize(boolean)

PersistentCollection.java:214

void net.sf.hibernate.collection.PersistentCollection.write()

PersistentCollection.java:84

boolean net.sf.hibernate.collection.List.add(java.lang.Object)

List.java:129

void mypackage.Prueba.main(java.lang.String[])

Prueba.java:45


This happens because I'm running evict on the parent object. If I comment the session.evict line it works.

Thanks in advance

Of course. This is correct behavior.

The error message is wrong.

The session is not closed. And I want to evict the object because I don't want Hibernate to serialize the object everytime I make changes and flush. Also I don't want to evict because I get problems serializing Oracle CLOBs and BLOBs. I already fixed this problem and part of the solution was to evict the objects.

So now I have two choices:

1.- I don't work with CLOBs or BLOBs, let Hibernate serialize everytime I flush and I can use lazy initialization.
2.- I work with CLOBs or BLOBs, I serialize when I want the application to serialize and I don't use lazy initialization.

I think that this problem can be solved if the application developer has some way to disable the mechanism that Hibernate uses to persist objects when they are updated. If I disable this mechanism I can store CLOBs and BLOB in Oracle without calling evict and still have lazy initialization.

Any reply from the Hibernate team?

Sorry about the rush but I'm in the middle of a project and this issue is important.