Hi,
I'm using a RequestCycleProcessor to provide a threadlocal-based
transaction to my application. I use something like:
protected IRequestCycleProcessor newRequestCycleProcessor() {
return new DefaultWebRequestCycleProcessor() {
You can either implement your transaction handling in your business
objects that are simply called from wicket or if you really want
transactional code in your pages you can subclass WebRequestCycle and
override the methods:
onRuntimeException() - rollback transaction
onEndRequest() -
use RequestCyle.onBeginRequest/onEndRequest for that.johanOn 5/11/06, Ralf Ebert [EMAIL PROTECTED]
wrote:Hi,I'm using a RequestCycleProcessor to provide a threadlocal-based
transaction to my application. I use something like:protected IRequestCycleProcessor newRequestCycleProcessor() {return new
Or hide your business logic in 'services' and make those
transactional. That gives you most control, but also is a bit more
work.
Eelco
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with
It's simple with Spring, but you don't need Spring for that...
You just need a thread local and a proxy around your services interfaces.
Then you wrap all services calls with proper transaction handling in the
proxy implementation.
I'm doing this with plain JDBC, its just a few lines.
-
