Since I'm connecting to a non-sql system and having only one system connecting to implementing this with wrap-servlet seems to be to complex. But I see that using a filter isn't a bad idea.
On Aug 20, 9:52 am, "Dhanji R. Prasanna" <[email protected]> wrote: > Check out warp-persist which provides all of this functionality for > you.http://www.wideplay.com/guicewebextensions2 > > <http://www.wideplay.com/guicewebextensions2>Dhanji. > > On Thu, Aug 19, 2010 at 9:21 PM, Johannes > <[email protected]>wrote: > > > Hi, > > > i need a kick start how do this "the guice way". > > > I have an api to an legacy system which has support for transactions. > > Now I want to write transactional servlets where fresh transactions > > automaticly get injected for each request and automaticly removed when > > the request is done. > > > My idea is to write a filter which adds a transaction to each new > > request and clean ups after the request is done. Is this the prefered > > way? Or are they better options? > > > J. > > > -- > > 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]<google-guice%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-guice?hl=en. -- 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.
