Ok, thanks.
It's just that the "page pool" feels like the JDBC "connection pool". :)
-Martin
On Mon, 24 Oct 2005 14:48:46 +0200, Norbert Sándor <[EMAIL PROTECTED]>
wrote:
You needn't, Tapestry will do it.
BR,
Norbi
----- Original Message ----- From: "Martin Strand"
<[EMAIL PROTECTED]>
To: <tapestry-user@jakarta.apache.org>
Sent: Monday, October 24, 2005 2:11 PM
Subject: Do I need to return the page to the pool?
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]
