Changes between Version 2 and Version 4 of Ticket #735

Timestamp:

11/07/07 11:33:41 (17 years ago)

Author:

jmoore

Comment:

This issue was not was to track down. The implementation of findContainerHierarchies walks a graph returned from Hibernate and rearranges the entities in a read-only graph. However, to prevent Hibernate from saving the rearragements, first the entities are evicted from the session.

The exception that's being thrown here:

ome.conditions.ValidationException: not-null property references a null or transient value: ome.model.containers.DatasetImageLink.details.creati
onEvent; nested exception is org.hibernate.PropertyValueException: not-null property references a null or transient value: ome.model.containers.DatasetImageLink.detail
s.creationEvent
        at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:628)
        at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:412)
        at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:377)
        at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:338)
        at ome.security.basic.EventHandler.invoke(EventHandler.java:160)
...

just says that one of the read-only links created for the read-only graph is missing some values. That's fine, we expect as much. The question is why is it even checking. Because an object is still reachable that shouldn't be.

Turns out the cyclical relationship image->defaultPixels->image is again causing problems (this will probably be removed in the next version.)

Fixed by r1921.