On this subject - I remember some time back we were discussing lift
run levels and potentially different errors / levels of logging for
different run levels. Did this ever come about?

Cheers, Tim

On Oct 2, 3:03 pm, TylerWeir <[EMAIL PROTECTED]> wrote:
> Hey Oliver,
>
> I dropped this in:
>       LiftRules.logAndReturnExceptionToBrowser = {
>         case (request, e) => println("what is going on");
> RedirectResponse("/");
>      }
>
> and wrote some jank code to force an exception and it's working as
> expected.
>
> What output are you not getting?
>
> On Oct 2, 7:22 am, Oliver Lambert <[EMAIL PROTECTED]> wrote:
>
> > I tried
>
> >      LiftRules.logAndReturnExceptionToBrowser = {
> >        case (request, e) => println("what is going on");  
> > RedirectResponse("/")
> >        case _ => println("whatis going on 2"); RedirectResponse("/")
> >      }
>
> > No change in behavior
>
> > On 02/10/2008, at 6:03 PM, Marius wrote:
>
> > > Or you can use LiftRules.logAndReturnExceptionToBrowser ...actually
> > > browserResponseToException  is ultimately called by
> > > logAndReturnExceptionToBrowser
>
> > > On Oct 2, 10:59 am, Marius <[EMAIL PROTECTED]> wrote:
> > >> Hi,
>
> > >> Please see LiftRules.browserResponseToException ... this is called
> > >> when an exception is thrown from the application. Here you can
> > >> "intercept" the Throwable and redirect to your own error page  using
> > >> RedirectResponse or RedirectWithState.
>
> > >> Br's,
> > >> Marius
>
> > >> On Oct 2, 10:48 am, Oliver <[EMAIL PROTECTED]> wrote:
>
> > >>> I don't want to display the default error page to the user. How do  
> > >>> I replace
> > >>> it with my own?
>
> > >>> cheers
> > >>> Oliver
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to