[WICKET-2165] Improve the API's Consistency and Flexibility With Respect to Generics and Collections

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4-RC2
• Fix Version/s: 1.4-RC3
• Component/s: wicket, wicket-extensions
• Assignee: Igor Vaynberg
• Reporter: James Carman
• Created: 13/Mar/09 04:38
• Updated: 24/Apr/09 08:54
• Resolved: 24/Apr/09 08:52

Description

There have been discussions about how collections are treated inconsistently in the Wicket API. For example, DropDownChoice allows a model of type IModel<List<? extends T>> and ListView only allows a model of type IModel<List<T>>. The most flexible approach for these situations (for the client code) is to allow IModel<? extends List<? extends T>>. However, merely synchronizing these two particular classes would leave other parts of the API inconsistent (Palette, ListChoice, ListMultipleChoice, etc.). What we need is a consistent approach to this situation across the entire API so that the API is more cohesive and understandable (if the user sees this weird syntax once they'll understand it everywhere).

Issue Links

• is duplicated by: WICKET-2163 Make Palette's "Choices" Model More Generics Friendly
• is related to: WICKET-2137 Synchronize generics between ListView and DropDownChoice