Comment #1 on issue 730 by spootsy....@gmail.com: Automatically started
UnitOfWork is never ended
http://code.google.com/p/google-guice/issues/detail?id=730
I've created a git patch which addresses this issue, as well as issue 731.
Rundown of changes from the commit log:
- JpaPersistService now counts invocations of begin() and end(), and only
closes
EntityManager when end() has been called an appropriate number of times
- Attempting to get an EntityManager outside of an active UnitOfWork now
results
in an IllegalStateException
- Added a new @WorkUnit annotation. This is equivalent to the @Transactional
annotation for methods/classes which access the database but do not
modify it
Patch also updates the appropriate unit tests.
Attachments:
0001-Updates-to-JpaPersistService-implementation-of-UnitO.patch 44.7 KB
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To post to this group, send email to google-guice-dev@googlegroups.com.
To unsubscribe from this group, send email to
google-guice-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-guice-dev?hl=en.
