Hmm. I just talked to Tyler and we found [in our app] some transactional services with methods that were decorated with [Transaction], but not declared virtual methods (which I am fixing right now). No exceptions were being thrown and the transaction was somehow getting committed anyway???
On Wed, May 6, 2009 at 3:09 PM, Jan Limpens <[email protected]> wrote: > They must be - otherwise the app would not run... > > 2009/5/6 Jonathan Vukovich <[email protected]> >> >> Tyler just reminded me about this the other day. >> >> Are you [Transaction] decorated methods declared as virtual? Could that be >> it? >> >> Thx! >> Jon >> >> >> On Wed, May 6, 2009 at 2:19 PM, Jan Limpens <[email protected]> wrote: >> > 2009/5/6 Tyler Burd <[email protected]> >> >> >> >> Are you by any chance using the HttpResponse.Redirect method? That >> >> throws >> >> a ThreadAbortException to end the request immediately, which will cause >> >> any >> >> transaction to fail. >> > >> > No, and anything that happens in the controller, that could possibly go >> > wrong is within try catch blocks (catch usually logs the exception and >> > gives >> > a frendly notification to the user what went wrong). >> > Hmm. Thinking about that - maybe this might be a problem. By not >> > exposing >> > the xxxDao.Save(obj) method, I probably never will have rollbacks. >> > Still I wonder why it would not commit. If every exception is caught, >> > every >> > transaction should be committed. >> > >> > I use JSONReturnbinder, but my guess is, that it uses the castle stack. >> > >> > -- >> > Jan >> > >> > > >> > >> >> > > > > -- > Jan > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
