[
https://issues.apache.org/jira/browse/WICKET-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681604#action_12681604
]
Brill Pappin commented on WICKET-2137:
--------------------------------------
I have to say that if its easier to regress the generics to the List<T>
version, then I think we should do that before 1.4 release... if as is thought
there the longer form is better and doesn't break code that uses the short
form, then we can add it after the 1.4 release.
That doesn't me we should choose one or the other now, I'm just interested in
the least possible change to make it right as the committers roll around to
releasing 1.4 (i think its essential that this get into the release).
As someone pointed out, we're in rc3 or rc4 now, so even the simplest change of
this sort is going to force people to do some fixing (better now than later
though).
So, whoever has to handle this issue, please make a choice for what ever is the
least hassle and bring the two components into sync.
> Synchronize generics between ListView and DropDownChoice
> --------------------------------------------------------
>
> Key: WICKET-2137
> URL: https://issues.apache.org/jira/browse/WICKET-2137
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4-RC3
> Environment: 1.4-SNAPSHOT as of 2009-01-28
> Reporter: Brill Pappin
> Attachments: TestGenerics.java
>
>
> DropDownChoice has a generics definition of List<? extends T> in its
> constructor.
> This causes trouble with existing models that may be used in a DropDownChoice
> and is not consistant with ListView which uses <List<T>>.
> Change DropDownChoice to match the other list type components so that their
> models can be used across components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
