You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/04/26 19:41:32 UTC
[jira] Resolved: (WICKET-2843) Palette is incompatible with
ListMultipleChoice in its use of the model
[ https://issues.apache.org/jira/browse/WICKET-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2843.
-----------------------------------
Assignee: Igor Vaynberg
Fix Version/s: 1.4.9
1.5-M1
Resolution: Fixed
> Palette is incompatible with ListMultipleChoice in its use of the model
> -----------------------------------------------------------------------
>
> Key: WICKET-2843
> URL: https://issues.apache.org/jira/browse/WICKET-2843
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4.7
> Reporter: Frank van Lankvelt
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.9, 1.5-M1
>
> Attachments: WICKET-2843.patch
>
>
> Palette, like the listmultiplechoice component, modifies the object (a list) in-place. Both components have the same behavior in their updateModel documentation, but the implementation differs. Whereas ListMultipleChoice invokes getModel().setObject(), Palette uses setDefaultModelObject(). This has the consequence that it never invokes the setObject method as that is guarded by a model comparator.
> Suggested fix is to use the same logic in both updateModel implementations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.