[
https://issues.apache.org/jira/browse/WICKET-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276600#comment-13276600
]
Gonzalo Aguilar commented on WICKET-4353:
-----------------------------------------
I've found similar problem.
It solves by just overriding the equals value in de options. But sometimes this
is not easy. For me it happens that the code that goes into the dropdown is an
autogenerated one with the XCF framework. It's the output of a Webservice and
makes it difficult to use.
I had to use a proxy class between dropdown and output. or override the
getModelValue function, what is not a good idea.
It should not use indexof. It should just compare choice renderer ids.
> Choice is not rendered as selected on different instances semantically equal
> ----------------------------------------------------------------------------
>
> Key: WICKET-4353
> URL: https://issues.apache.org/jira/browse/WICKET-4353
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4
> Environment: windows, jdk1.6
> Reporter: Per Newgro
> Labels: DropDownChoice
> Attachments: ddcbug.zip
>
>
> With 1.5.4 there was a change in
> org.apache.wicket.markup.html.form.AbstractSingleSelectChoice.java
> Sven stated in list that: "Igor's commit statements says "improved
> inconsistency handling in choice components".
> This change prevents IChoiceRenderer#getIdValue() being called with -1 as the
> index argument. ".
> It is defenitly a comprehensible change. But the effect is (for me) quite
> heavy.
> If you don't overwrite equals in selectable objects then two semantically
> equal instances will not be rendered as
> selected because of the different physical instances. But it worked in 1.5.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
