How do you support transactions now? Traditionally, there's a wrapper class with Template Methods providing the begin, execute, end sequence and commit/rollback handling. CP30's connection pooling has worked great and deals with reconnects, stale connections, etc. without much customizing at all.
In and of itself, Guice won't provide much unless there's a JDBC abstraction layer (Templatized DAO's for instance) for it to work with. We have such here, so Guice affords us the ability to just swap out ConnectionPool's, Transaction Strategies, etc.. simply by using different Guice Modules. On Feb 27, 7:01 pm, Karthik Krishnan <[email protected]> wrote: > Hi All, > > In our application, we are slowly migrating to Guice from no DI but we > have hit a little bit of a road block. In our application, we use > CallableStatement to make database calls and not any persistence API. > Is there any guice based application that we can use for transactional > support. I know that warp api is used to support Hibernate, JPA and > and DB4Objects. > > A post on Stack > Overflowhttp://stackoverflow.com/questions/2347384/guice-jdbc-and-managing-da... > did not return any answers as yet. Dhanji's > blogshttp://www.jroller.com/dhanji/ > andhttp://rethrick.wordpress.com/did not help with that either. > > Has any one done any plain jdbc set up with Guice? > > Thanks, > > Kartik -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
