any ideas about my question?
Thanks very much
Il giorno giovedì 16 agosto 2012 00:57:02 UTC+2, bond ha scritto:
Hi Thomas,--
thanks for your reply. My problem is not use or not use a Filter to solve this problem. My problem is try to send exception caugth in PersicensteFilter on the client. I need a per request session and transaction.
If my problem was only lazy inizialization of course this method is not necessary. I've many entity with complex fields and when I persist, RF calls automatically findById that raise org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session. So I need that when I call a method on RF all go in a unique session and transaction.
Thanks very much
Daniele
Il giorno martedì 14 agosto 2012 17:13:55 UTC+2, Thomas Broyer ha scritto:You're trying to solve the wrong problem. If you have an issue with lazy loading, then load eagerly, do not extend your transaction lifetime.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/lHqqwPQ2xc0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment