Closed GoogleCodeExporter closed 9 years ago
Thanks for reporting this. It's normal that you need the additional
configuration for
class level @Transactional. Other than that, this is an issue on the Guice side:
http://code.google.com/p/google-guice/issues/detail?id=149. Please comment on
that
issue so that they are aware of your problem.
Your JUnit jar is probably signed, so then you have some options:
- Remove the signing information from junit.jar (or build from src)
- Sign the Guice jar with the same key JUnit uses.
- Patch Guice so that its Enhancer uses a custom namingpolicy that puts all
generated
classes in a different package.
You could also have a look at the various testing frameworks that come with
Guice
integration like GuiceBerry or AtUnit. Maybe that's what you're looking for?
Original comment by robbie.v...@gmail.com
on 1 Jan 2009 at 7:08
Original issue reported on code.google.com by
doug.sat...@ymail.com
on 1 Jan 2009 at 12:00