panpan wrote:
>
> The session is open, why do I need to reattach them?
>
You wouldn't need to if you loaded and discarded your objects in a single
request, but let's say you have objects that lived around longer than a
single request ( i.e., a User object in your http session ). You might
have reattached this object to the session every time you wanted to make a
modification to it, because you were creating hibernate sessions on the fly.
With OSFV, you might end up with errors because after the first time, the
object is already attached to the session.
That's probably the most common use case.
panpan wrote:
>
> And could you please be more specific about the 'watch transaction
> boundaries'. Sorry, that might be stupid questions.
>
What i meant by watch transaction boundaries is simply take note where and
how you decide to mark off a transaction. For example, if you weren't using
Spring's declarative ( or aop-based ) transaction management, you might have
a session.beginTransaction() in one method, and a session.endTransation() in
another method. If you were creating hib sessions on the fly, if you rolled
back, you can simply wipe out your session and create a new one and go on
your (relatively) merry way. With OSFV, that session that you rolled back
against is still there, so maybe your objects that you haven't persisted are
not in the db, but still associated with a session. The same thing can
obviously occur with Spring's transaction management as well, but at the
heart of it, I meant that's something to keep in mind.
panpan wrote:
>
> Really appreciate your help and time.
>
Always a pleasure.
-a
--
View this message in context:
http://www.nabble.com/-S2--how-to-configure-Spring%27s-OpenViewInSessionInterceptor-for-struts2-tf4050042.html#a11508627
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
