Re: intercepting page rendering

2006-04-10 Thread Aleksej
If you only need to have transaction opened during page rendering then you should put your logic into separate hivemind service with threaded model. Such service must start transaction at initialization and close it in the end of thread ( after page rendering ). Look more in hivemind docs. ---

Re: intercepting page rendering

2006-04-10 Thread Ted Steen
As I understand, the rewind cycle updates properties and if there is an active transaction these changes could be persisted without my knowing? or am I wrong? What I want is to make the transaction only span the part of the rendering that has to do with reading, so that no properties will be persi

Re: intercepting page rendering

2006-04-10 Thread Henri Dupre
With my solution, the request would span the rewinding + page rendering... Why don't you want the transaction to span the rewinding? I'll post on the wiki my solution. Henri. On 4/10/06, Ted Steen <[EMAIL PROTECTED]> wrote: > > Hi Henri. > > I got a solution that provides the session (in a sessi

Re: intercepting page rendering

2006-04-10 Thread Ted Steen
Hi Henri. I got a solution that provides the session (in a session-per-view manner). I also have transaction-handling (using interceptors). Problem now is that there must be a transaction open while rendering the page, for being able to lazy-load collections, etc. I do not want the transaction to

Re: intercepting page rendering

2006-04-10 Thread Henri Dupre
I wouldn't suggest to hack into the page rendering... This lead into most of my poor code in Tapestry 3 that I'm trying to cleanup... What I did in Tapestry 4 is a WebRequestFilter that creates a Spring Hibernate session (I translated the Spring "OpenSessionInView" servlet filter). If you are using

intercepting page rendering

2006-04-10 Thread Ted Steen
Hi all! I need an active transaction when the page is rendered, in order to load/read lazy collections. One way to do it would be to start a transaction in beginRender etc. Another way that I think is better would be to intercept the method in the Engine that renders the page. Now the problem is t