Re: flow: release resources after the view is generated

2004-06-14 Thread Sylvain Wallez
Vadim Gritsenko wrote: Sylvain Wallez wrote: Vadim Gritsenko wrote: What worries me is that sendPageAndWait provides an argument, which is reference to the cleanup function. AFAIU, this function should be invoked after page is sent. If you take a look at sendPageAndWait, it looks like:

Re: flow: release resources after the view is generated

2004-06-13 Thread Sylvain Wallez
Vadim Gritsenko wrote: What worries me is that sendPageAndWait provides an argument, which is reference to the cleanup function. AFAIU, this function should be invoked after page is sent. If you take a look at sendPageAndWait, it looks like: FOM_Cocoon.prototype.sendPageAndWait = function(uri,

Re: flow: release resources after the view is generated

2004-06-13 Thread Vadim Gritsenko
Sylvain Wallez wrote: Vadim Gritsenko wrote: What worries me is that sendPageAndWait provides an argument, which is reference to the cleanup function. AFAIU, this function should be invoked after page is sent. If you take a look at sendPageAndWait, it looks like:

Re: flow: release resources after the view is generated

2004-06-11 Thread Jeremy Quinn
Hi Guys, catch (return) {session.close ()} has worked fine when I needed it in the past. What confused me about it was that the 'catch' statement is not paired with a 'try' or a 'finally' statement it sits by iteslf. HTH regards Jeremy On 10 Jun 2004, at 09:15, Reinhard Poetz wrote: Leszek

Re: flow: release resources after the view is generated

2004-06-11 Thread Leszek Gawron
Jeremy Quinn wrote: Hi Guys, catch (return) {session.close ()} has worked fine when I needed it in the past. What confused me about it was that the 'catch' statement is not paired with a 'try' or a 'finally' statement it sits by iteslf. To be sure: does it also work with cocoon.sendPage() ? --

Re: flow: release resources after the view is generated

2004-06-11 Thread Jeremy Quinn
On 11 Jun 2004, at 10:56, Leszek Gawron wrote: Jeremy Quinn wrote: Hi Guys, catch (return) {session.close ()} has worked fine when I needed it in the past. What confused me about it was that the 'catch' statement is not paired with a 'try' or a 'finally' statement it sits by iteslf. To be sure:

Re: flow: release resources after the view is generated

2004-06-10 Thread Reinhard Poetz
Leszek Gawron wrote: One of the users had reported an example that needs resolving. As it is something that affects also me I didn't want to wait for him to post some questions. Imagine you obtain some resources that need to be valid during view rendering. A hibernate session is a good

flow: release resources after the view is generated

2004-06-09 Thread Leszek Gawron
One of the users had reported an example that needs resolving. As it is something that affects also me I didn't want to wait for him to post some questions. Imagine you obtain some resources that need to be valid during view rendering. A hibernate session is a good example. You need to have