In a related vein, where would you suggest starting & ending JTA
transactions (or Hibernate transactions or whatever).  Something like
99+% of the time transactions should start with the client request and
end with the client request -- whether that's Wicket or Swing or
whatever.  Multiple transactions (except for nested transactions for
things like logging) are almost always a mistake and transactions
spanning multiple client interactions are even more often a mistake.

Is #onBeginRequest and #onEndRequest a reasonable place to begin/end
transactions -- or are there transaction management hooks otherwise in
place in Wicket?

Thanks,
Scott

On 10/23/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> On 10/23/06, Carfield Yim <[EMAIL PROTECTED]> wrote:
> > > And in fact I'm wondering what that component manager is doing anyway?
> > > As this would be more typical:
> > >
> > Look like we've some misunderstanding here, the component manager is
> > something that return a service for my old application. Where a
> > service in that application like an Object of Page in wicket. So the
> > idea is just every time a before a page render and after a page
> > render, or doing the operation. Run some setup before and cleanup
> > afterward.
>
> Yeah, I expected it was something like that, hence the second example I gave.
>
> This is a typical example of 'the unlearning effect' people go through
> when used to developing with frameworks like Struts etc. Basically,
> you have to let go of the request/response way of programming you
> would do with other frameworks. Just try to code like you can see in
> the examples etc.
>
> > Yes, just figure out that, post it here please let me know if I am wrong:
>
> You should provide instances of WebRequestCycle rather then
> RequestCycle directly. And then let the super class handle things like
> onRuntimeException and getRedirect, and only override those methods
> you really need.
>
> But again, instead of starting in this direction, postpone until you
> are really sure you need a custom request cycle. In 99% of the case
> you won't need it, and instead should focus on components instead.
>
> Eelco
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>


-- 
Scott Swank
reformed mathematician

Power is not a means, it is an end. One does not establish a
dictatorship in order to safeguard a revolution; one makes the
revolution in order to establish the dictatorship. The object of
persecution is persecution. The object of torture is torture. The
object of power is power.  -- George Orwell, 1984

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to