Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.1-beta1
-
Component/s: Persistence
-
Labels:None
Description
It looks like I get a side effect of discard(): an exception is thrown in my gsp after I call discard on the object passed to the gsp: Hibernate cannot lazily load a Set property of the object, complaining the session is closed. I ended up by doing a obj.refresh() to solve the issue but I am wondering if it is clean to do so.
Thanks
Fred
================================================================
Graeme Rocher <graemerocher@yahoo.co.uk> to user
This is a bug, please raise an issue
It doesn't close the session, but it evicts the object. save() used to
do this on validation failure, but we corrected the problem
I can confirm this issue for a June SVN snapshot of Grails 1.0.3.
This is a serious problem, any workarounds?