On Thu, May 7, 2009 at 9:17 AM, Timothy Perrett <timo...@getintheloop.eu>wrote:
> > Are you talking about errors in production? My advice would be to > write an implementation of ExceptionHandlerPF and then you can do > whatever you want based on run.mode or whatever. Yep... this is much like the other exception handling question that came up this morning. If you guys need an example of a handler, please let me know and I'll work something up. > > > Logging wise, were using Log4J so you could just add another log > descriptor if you want file logging as well as console logging. > > Cheers, Tim > > On May 7, 4:33 am, g-man <gregor...@gmail.com> wrote: > > I'm having a great time learning Lift, and am happy to read all the > > excellent posts by the growing community of developers... > > > > As I experiment and create my app, I naturally get errors, and I was > > wondering if Lift has, or has considered, an 'error ticket' system > > like web2py has, where the user never sees an error, but a ticket is > > created, which is a link to an admin directory (templates-hidden?) > > where the actual error stack trace is saved. > > > > Otherwise, all is well! > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
