The @Retry just calls the method again if exception is thrown. Just need to make sure the RetryInterceptor is the first one installed to avoid any surprises.
In my case the database server got restarted from time to time. That is nothing special but didn't want the Connection Pool to validate connections all the time, therefore ConnectionClosedException happens. But the @Retry just calls the method again, the CP is smart enough to give a good connection the second time, and the user doesn't get en error. Cheers Alen On 1 mar., 16:46, Kartik Kumar <[email protected]> wrote: > @Alen What is @Retry annotation? Was this one of the application specific > annotations that you implemented? > > On Sun, Feb 28, 2010 at 3:11 PM, Eelco Hillenius > <[email protected]>wrote: > > > > > > Just curious, when would you not need a transaction? > > > I guess I should say that you don't always want to turn off autocommit > > (transaction per execution instead of per annotated method). And > > thinking about it it, maybe there is no good reason. > > > Eelco > > > -- > > 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%2bunsubscr...@google > > groups.com> > > . > > 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.
