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 of exception, roll back the transaction + propagate
exception
<filter>
<filter-name>LiftFilterTransactionWrapper</filter-name>
<filter-class>services.LiftFilterTransactionWrapper </filter-
class>
</filter>
<filter-mapping>
<filter-name> LiftFilterTransactionWrapper </filter-name>
<url-pattern>/messagebroker/*</url-pattern>
</filter-mapping>
class LiftFilterTransactionWrapper ... {
...
}
This will be just enough.
What should be inside LiftFilterTransactionWrapper?
--
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
-~----------~----~----~----~------~----~------~--~---
