On Sep 15, 5:52 pm, Thomas Broyer wrote:
> You should make one sub-interface of AValueProxy per type of
> AGenericEntityProxy that you'd use for its T type parameter; remove the type
> parameter (making AValueProxy no longer generic), and using @ExtraTypes (GWT
> 2.4 onwards) for polymorphism, lis
The issue you point me to is probably related, since I have a
Request>>...
Thank you for the fast response. I'll look the docs for what you
suggest me and see how it fits. Currently the project I'm working with
is using GWT 2.3, so I don't even know if I'll be able to use it,
let's see.
Thanks ag
I think it is (illegal).
You should make one sub-interface of AValueProxy per type of
AGenericEntityProxy that you'd use for its T type parameter; remove the type
parameter (making AValueProxy no longer generic), and using @ExtraTypes (GWT
2.4 onwards) for polymorphism, listing the sub-interfac
A little bit more information I've gathered with a debugger:
At a certain moment, TypeUtils.getParametrization is called with a type that
is a TypeVariable of value T. That method doesn't deal with such types, and
returns null.
The result of the request where this happens is a
List> where the ent
