if you make it pragmatically configurable then it shouldnt matter what IOC you use, after all thats the point. i think @Transactional is pretty much a standard by now and you can make that work via guice or spring or any other aspect you want to have in your environment....
-igor On Tue, May 20, 2008 at 2:54 PM, Uwe Schäfer <[EMAIL PROTECTED]> wrote: > Peter Ertl schrieb: >> >> guice DOES support @Transactional (and any other AOP Alliance interceptor) >> it's called AbstractModule.bindInterceptor() > > actually, there are quite a few frameworks on top of guice using this to > implement the exact same @Transactional behaviour. > > shouldn´t it be quite simple to opt this out? > if not, i could live with JPA & Guice, because this is *my* current toolset > ;) > > seriously: guice can happyly coexist with spring afaik, and any serious ORM > implements JPA1.0 (hope, those JDO guys wont strike me down now). > > would it be an option to choose guice for INTERNAL DI and rely on JPA? > > @Spring guys: yes, we´d have @Tranactional, OpenEMInView and something > similar to JPATemplate as well as a little criteria API, then. > > cu uwe > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]