You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tapestry.apache.org by "Filip S. Adamsen" <fi...@stubkjaer-adamsen.dk> on 2004/08/25 15:27:14 UTC

RE: do java classes and properties need to be abstract for anyparticular reason?

> -----Original Message-----
> From: Jonny Wray [mailto:jonny_wray@yahoo.com]
> Sent: Wednesday, August 25, 2004 5:39 AM
> To: Tapestry users
> Subject: Re: do java classes and properties need to be abstract for
> anyparticular reason?
> 
> 
> [...]
> 
> It works well - you end up more or less forgetting about the pooling
> mechanism in day to day work.
> 

What pooling mechanism? ;o)

> [...]




---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org