Hi,
Both you and Thiago are of course right. I just remember Howard saying
something about this being very difficult to do. Probably has something
to do with Javassist.
-Filip
On 2008-07-29 05:30, Ivan Dubrov wrote:
Filip S. Adamsen wrote:
Hi,
As far as I know it's very difficult - if not
Filip S. Adamsen wrote:
Hi,
As far as I know it's very difficult - if not impossible - for
Tapestry to support generics in method parameters because of the way
generics are implemented in Java (type erasure).
A lot of type information is still available through reflection.
Assuming concrete
Em Mon, 28 Jul 2008 13:13:21 -0300, Filip S. Adamsen <[EMAIL PROTECTED]>
escreveu:
As far as I know it's very difficult - if not impossible - for Tapestry
to support generics in method parameters because of the way generics are
implemented in Java (type erasure).
Not every type informatio
Hi,
As far as I know it's very difficult - if not impossible - for Tapestry
to support generics in method parameters because of the way generics are
implemented in Java (type erasure).
-Filip
On 2008-07-28 15:44, Thiago H. de Paula Figueiredo wrote:
Em Mon, 28 Jul 2008 10:33:46 -0300, Moritz
Em Mon, 28 Jul 2008 10:33:46 -0300, Moritz Gmelin <[EMAIL PROTECTED]>
escreveu:
public abstract SuperClass {
public abstract void onActivate(E value);
}
public SubClass Extends SuperClass {
public void onActivate (Bar value) {
System.out.println ("Here i am " + value);
}
T
Hi,
if I have an abstract superclass of a page that has the abstract
definition of onActivate() defined
public abstract SuperClass {
public abstract void onActivate(E value);
}
and a subclass
public SubClass Extends SuperClass {
public void onActivate (Bar value) {
System.o
