Well, typically the form callbacks are just setting values. If they're more complex than that then you would need a try/catch in each function. I don't think that the current form processing code has any facility for a per-form exception handler, although that might be a useful feature.
Derek On Tue, May 19, 2009 at 1:09 PM, ngug <naftoli...@gmail.com> wrote: > > Sorry for the delay in responding. My question was not about > transaction API, my question was a practical one: If form processing > is split into a bunch of little anonymous functions, how can you put > them in a try/finally? > > On May 15, 1:59 pm, Derek Chen-Becker <dchenbec...@gmail.com> wrote: > > EntityManager has a getTransaction method that you can use along with the > > constructor I mentioned previously to explicitly begin and end > transactions > > in your code. > > > > derek > > > > On Fri, May 15, 2009 at 11:45 AM, ngug <naftoli...@gmail.com> wrote: > > > > > One entity group per transaction is a GAE requirement. But my question > > > about handling transactions was more specific - because form > > > processing is specified "piecemeal" in separate closures, you can't > > > use the normal try/finally. It seems a little too much effort to > > > create a hidden field before and after every form/"subform". > > > Thanks. > > > P.S. Sorry about the triple post. Opera Mobile (well, Google) didn't > > > tell me the post was successful like it usually does, so I thought it > > > didn't go through. (I thought the list is moderated and you would > > > filter the extras just in case.) > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
