I think tapestry handles it in a threaded model, so when your thread
ends the page will return to the pool.
ציטוט Martin Strand:
Hi.
I'm using a login listener that does something like this:
----------------------------------
try
{
page = cycle.getPage(...);
page.login(...); // throws AuthenticationException
return page;
}
catch (AuthenticationFailedException e)
{
// --> Is a cleanup necessary here?
return null;
}
----------------------------------
If I get a page with getPage(), and then an AuthenticationException is
thrown, don't I need to return that page to the pool again somehow?
--Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]