Newly set quantum strategy fails on flush.

[jburel]

Crash when setting the new quantum strategy i.e. a new bit resolution. Below the error message:Caused by: ome.conditions.InternalException?: Wrapped Exception: (org.springframework.orm.hibernate3.HibernateSystemException?): not-null property references a null or transient value: ome.model.display.QuantumDef?.details.owner; nested exception is org.hibernate.PropertyValueException?: not-null property references a null or transient value: ome.model.display.QuantumDef?.details.owner

at org.springframework.orm.hibernate3.SessionFactoryUtils?.convertHibernateAccessException(SessionFactoryUtils?.java:654)

[jburel]

Oops forgot to log in before entering ticket ;-)

[jmoore]

This is being caused by furtive flushings of the stateful bean. It shouldn't happen. Period. Will fix.

[jmoore]

r837 fixes. Some of this comes from not being able to test the rendering bean from trunk (#218). In general, the stateful session handling needs work, and only time and testing will test.

What this fix does is changes the use of FlushMode.NEVER (which Hibernate kindly deprecated from under us) to FlushMode.COMMIT, and added a check in EventHandler to not call flush if the interceptor joinpoint is a StatefulServiceInterface implementation. (Having that logic in the handlers is typically valid. Written up as #262)

[jmoore]

r1039 updates the FlushMode? to MANUAL (NEVER is deprecated) and makes fixes for Spring 2.0 (#238), which handle the FlushMode?'s differently (especially now with JTA -- #427)