David,
> Your call to Service.say is outside the scope of the Lift HTTP request, so
> it's not wrapped with the transaction management stuff.
Exactly.
The thing that I want LiftFilter to wrap "/messagebroker/*", so I will
get per-HTTP request
automatic transaction management and my code will remain clean.
LiftFilter 0.9 and BlazeDS worked perfectly together,
but when I switched to Lift 1.0 and greater, LiftFilter killed
BlazeDS.
Removing mappings from "web.xml" or adding
"LiftRules.liftRequest.append { case Req("messagebroker" :: _, _, _)
=> false }"
didn't really solved the problem but diverged it: BlazeDS is alive,
but it made nice features of Lift useless.
I believe that these are attempts to cure symptoms while disease is
still here: LiftFilter kills BlazeDS.
It would be great to have a solution like this:
- LiftFilter wraps "/messagebroker/*" but doesn't change requests, so
BlazeDS servlet still working
- methods like Service.say gain transaction management from Lift and
its code remains clean
--
Oleksandr
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
