a compilation error is also a deal breaker. 1.4.x should be dropin replacements.
we will have to wait for 1.5 to get this in. hopefully, this time
around 1.5 will be a much shorter cycle.
-igor
2009/8/8 Uwe Schäfer <u...@thomas-daily.de>:
> Igor Vaynberg schrieb:
>
>> what happens if you overrode a method that took a map<string,object>
>> and then change the super to map<string,?> ?
>
> while it certainly does no longer compile
>
> "Name clash: The method foo(Map<String,Object>) of type C has the same
> erasure as foo(Map<String,?>) of type A but does not override it"
>
> it still looks like working. here´s what i tested with:
>
> public class A{
> public void foo(final Map<String, ?> bar) {
> bar.clear();
> }
> }
>
> and in different project
>
> public class B{
> public static void main(final String[] args) {
> final Map<String, Object> a = new HashMap<String, Object>();
> new C().foo(a);
> }
> }
> class C extends A{
> �...@override
> public void foo(final Map<String, Object> bar) {
> super.foo(bar);
> }
> }
>
> cu uwe
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
