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
Hello David,
May be there can be a compromise solution.
A custom filter that has only these duties:
- to open LiftMapper-compatible transaction on HTTP-request (it will
be accessible from DB entities like User)
- call chain
- when all chain was processed
+ commit the transaction
+ in case
Query SELECT user_t.id FROM user_t
6 Query commit
=
Basically it behaves like when LiftFilter url mapping was commented in
web.xml.
I have updated http://github.com/oshyshko/lift_vs_blazeds
To reproduce it:
1. mysql - create
, 2009 at 10:14 PM, oshyshko oshys...@gmail.com wrote:
Looks like S.addAround(DB.buildLoanWrapper) has no effect.
What code are you using to make the query?
Please create a fully running example (making a GitHub project is the best
way to do this) so that I can see exactly what is happening
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.
Looks like net.liftweb.http.LiftFilter after version 1.0.+ breaks
BlazeDS servlet.
Version 0.9. of net.liftweb.http.LiftFilter works fine.
I want to switch to a newer version of Liftweb, but I can't.
Any ideas how to make LiftFilter 1.0.+ to work with BlazeDS servlet?
More info:
I used Scala
