Not sure why Select and not the others.  I've been struggling to come
up with a strategy for components that will help maintain backwards
compatibility.  I've nervous that using existing components as base
classes opens up future code to the fragile base class problem, as was
the case in Tapestry 4 and earlier.

On the other hand, the ability to extend components is a compelling feature.

On Thu, Feb 28, 2008 at 1:55 PM, Sven Homburg <[EMAIL PROTECTED]> wrote:
> has anybody an answer for that?
>
>  --
>  with regards
>  Sven Homburg
>



-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to