[
https://issues.apache.org/jira/browse/WICKET-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-3129.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg
for this kind of behavior we have CheckGroup/Check components
> CheckBoxMultipleChoice should be more expandable
> ------------------------------------------------
>
> Key: WICKET-3129
> URL: https://issues.apache.org/jira/browse/WICKET-3129
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.12, 1.5-M2.1
> Reporter: Joonas Koivunen
> Assignee: Igor Vaynberg
>
> Looking at the source code of this component the only way to provide custom
> Label's per generated <input type="checkbox"/> seems to be to have them as
> siblings of this component AND have a IChoiceRenderer that will return *null*
> display values.
> A non-breaking change would be that the
> CheckBoxMultipleChoice#onComponentTagBody would NOT replace it's body IFF it
> has children and all returned display values were null's.
> That would allow user to add for example RefreshingView<T> to produce <input
> /><label /> for the component, if the user wants to use other <label> or
> input compents.
> Another solution could be adding a boolean property to control whether user
> is expected to provide the labels manually, onComponentTag or
> onComponentTagBody would then assert that the component has children.
> I can provide a patch if either solution sounds reasonable.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
