Note that you will also have to deal with lazy loading (if you use it) for references or collections of references. This is easier as you only have to call session.lock(object, LockMode.NONE).
This is a compulsory dependency when working with Hibernate lazy loading, due to the way it handles its own sessions (so you end by never having a completely independent presentation layer, as ideal architectures claim).
Regards,
Quique.
On 3/3/06, Sebastien Boutte <[EMAIL PROTECTED]> wrote:
Enrique,
I think that i have to redesign some part of my code, to integrate
completely with Spring.
I will retest after that refactoring task.
Thank you
Sébastien
The problem must be that you are using request-scoped beans, don't you?
If you use request-scoped beans, then you have to "merge" on every request,
using session.merge ;-)
There was a discussion about this issue at the beginning of February:
http://marc.theaimsgroup.com/?l=myfaces-user&m=113890037426173&w=2
I would recommend using either session-scoped beans, or a session state
container, accesible to all your beans, where the current object being
worked is available.
