Removing BlazeDS servlet from LiftFilter coverage is a bad idea: If it is done so, lift-mapper creates separate transactions for all operations.
http://groups.google.com/group/liftweb/browse_thread/thread/e2c0dd2c5dcc458b This means LiftFilter and BlazeDS servlet should become friends. "LiftRules.passNotFoundToChain = true" is in my Boot.scala. The response is: ================================ HTTP/1.1 200 OK Expires: Thu, 01 Jan 1970 00:00:00 GMT Set-Cookie: JSESSIONID=1a8mg0498vrwd;Path=/ Content-Length: 0 Server: Jetty(6.1.21) ================================ Note: if I remove LiftFilter, the servlet works fine. Any ideas how to make LiftFilter not to intrude into BlazeDS deeds? On Oct 31, 2:19 pm, Timothy Perrett <[email protected]> wrote: > You needed to specify the passNotFoundToChain var, thats why you were > getting the 404 originally - as you detail, its not needed to > explicitly set the /messagebroker URL in your web.xml. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
