I've just updated my code to rely on the stable version of lift 0.10
rather than an earlier snapshot.
Unfortunately the removal of LiftRules.logAndReturnExceptionToBrowser
and non working status of
LiftRules.exceptionHandler.prepend means my choices now are
1) To back out my reliance on the stable version of lift 0.10
2) To look at the source code for lift and try to figure out the problem
3) To remove my applications reliance on this code
I am going to be glad when Lift gets to version 1.0, because
presumably there will be less breaking changes (I hope)
On Wed, Feb 11, 2009 at 9:58 AM, Oliver <ola...@gmail.com> wrote:
> Doesn't look right and If I do this I get the following error -
> constructor cannot be instantiated to the expected type
>
> On Tue, Feb 10, 2009 at 8:57 PM, Jorge Ortiz <jorge.or...@gmail.com> wrote:
>> Try (without the = sign):
>>
>> LiftRules.exceptionHandler.prepend {
>> case (mode, state, ex) => RedirectResponse("/error")
>> }
>> --j
>>
>> On Mon, Feb 9, 2009 at 10:47 PM, Oliver <ola...@gmail.com> wrote:
>>>
>>> If I try to use the following, I get a reassignment to Val error - any
>>> ideas?
>>>
>>> LiftRules.exceptionHandler.prepend = {
>>> case (mode, state, ex) => RedirectResponse("/error")
>>> }
>>>
>>> On Wed, Dec 24, 2008 at 5:41 AM, Marius <marius.dan...@gmail.com> wrote:
>>> >
>>> > Folks,
>>> >
>>> > I just committed a couple of changes that may impact your application.
>>> >
>>> > 1. LiftRules.logAndReturnExceptionToBrowser and
>>> > LiftRules.browserResponseToException have been removed. These were two
>>> > different variables that did pretty much the same thing in fact the
>>> > first ultimately called the former. These have been replaced with:
>>> >
>>> >
>>> > var exceptionHandler = RulesSeq[ExceptionHandlerPF]
>>> >
>>> > having
>>> >
>>> > type ExceptionHandlerPF = PartialFunction[(Props.RunModes.Value, Req,
>>> > Throwable), LiftResponse]
>>> >
>>> > By default a partial function is appended and it is the same code that
>>> > used to be for LiftRules.browserResponseToException.
>>> >
>>> > So up until now probably your application was using something like:
>>> >
>>> > LiftRules.logAndReturnExceptionToBrowser = {
>>> > case (state, ex) => RedirectResponse("/error")
>>> > }
>>> >
>>> > now this turns into:
>>> >
>>> > LiftRules.exceptionHandler.prepend = {
>>> > case (mode, state, ex) => RedirectResponse("/error")
>>> > }
>>> >
>>> >
>>> > 2. More unification of Ajax notices with "static" notices. So far to
>>> > apply styling information (css classes etc) to Ajax notices we used
>>> > three LiftRules variables:
>>> >
>>> > var ajaxNoticeMeta: Can[AjaxMessageMeta]
>>> > var ajaxWarningMeta: Can[AjaxMessageMeta]
>>> > var ajaxErrorMeta: Can[AjaxMessageMeta]
>>> >
>>> > the motivation was that in order for Lift to send down the correct
>>> > style information for Ajax/Comet notices it needed to maintain this
>>> > information. Now I finally found time to do it. The above variables
>>> > are gone. Instead the same styling information that you use for
>>> > lift:msgs and lift:msg snippets will be applied for AJax and Comet
>>> > notices. The styling information is captured when these snippets are
>>> > executed and used whenever you're using notices for AJax response or
>>> > from a Comet actor.
>>> >
>>> >
>>> > Br's,
>>> > Marius
>>> > >
>>> >
>>>
>>>
>>
>>
>> >>
>>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
