Comment #8 on issue 597 by [email protected]: Persist Extension:
UnitOfWork.begin() throws IllegalStateException when called multiple times
http://code.google.com/p/google-guice/issues/detail?id=597
I really think that introducing in Guice Persist any kind of checking
whether unit of work has already begun is a bad idea:
1) That's the whole point of Unit Of Work pattern: the user is responsible
for explicitly starting it and ending it as well. If it fails to do so,
that's not a bug in Guice Persist, that's a bug in the user's code or other
libraries;
2) If we reuse an existing unit of work, we kind of hijack an existing
(most probably not flushed) ORM session which could be a cause for much
more obscure bugs than those people are describing here.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.