[WICKET-4963] ComponentModel "setObject" methods should take generic "T" type instead of "Object"

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 6.4.0
• Fix Version/s: 6.5.0
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Ota Hauptmann
• Created: 10/Jan/13 13:57
• Updated: 10/Jan/13 17:23
• Resolved: 10/Jan/13 17:23

Description

ComponentModel implements public final void setObject(Object object), although the parameter should be "T object". This expansion of type seems to be useless and it looks like forgotten piece of code from Wicket version which did not support generics.

The same issue is with protected setObject(Component component, Object object) and the private inner WrapModel.

Note: This issue also causes an issue with IntelliJ IDEA, which reports a method clash of ComponentModel and IModel because of same erasure (when creating a subclass of ComponentModel). It is possibly IDEA bug, because compilers have no problem with it, but it doesn't change the fact that the setObject signature is at least strange.

I have tried to find this in JIRA, but unsuccessfully (so please accept my apologies whether I missed it only). The only "info" I have found was this: http://osdir.com/ml/users-wicket.apache.org/2009-05/msg01176.html