I'm not sure how much of the generics type information is carried
forward to runtime;
Basically all of it, but supporting it does indeed create dependancies
on Java5 and that was not what I was after, since I understand that
would have a huge impact on backward compatibility. What I am looking
for is for a work-around: A way to define the type for the key in each
subclass like it used to be possible for T3. That way the base class can
still use generics, but the developer is responsible for defining the
proper type in the sub-pages' property-specification to override the
default 'Object'-type?
... and require JDK 1.5 for Tapestry, something that sends people into fits
when you even suggest it.
I can imagine, although I would personally never want to look back to
older VM's anymore for web-development :oP
Regards,
Onno Scheffers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
