hi igor,
i dont think we are cutting anything out. i am sure i can still come up with examples where generics do not work on component or model: such as a model that returns different-typed objects based on some condition.
that's actually a quite different case than this, since here there are no conditions to be evaluated.
in these cases you simply use the raw types and supress the warning. why can you not do that for your particular usecase?
the point of using generics is to provide type safety and don't have to assume types using casts. in my case it's breaking a structure i set up not to have to cast when using generics. i'll send you a pm example how that works for me.
best regards, --- jan.
