[
https://issues.apache.org/jira/browse/WICKET-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alastair Maw resolved WICKET-402.
---------------------------------
Resolution: Won't Fix
I get your reasoning, really I do. ;-) However, most of the time, the use case
for this component is very much not just to update the model. Providing an
abstract onUpdate() method makes things easier to use, as it's obvious what to
implement.
If you find yourself doing this often in your project, you can of course create
a NoOpAjaxCheckBox or whatever, which will do this for you.
> AjaxCheckBox should not be abstract
> -----------------------------------
>
> Key: WICKET-402
> URL: https://issues.apache.org/jira/browse/WICKET-402
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 2.0 branch (discontinued)
> Reporter: Brian Topping
> Priority: Minor
> Attachments: AjaxCheckBox.patch
>
>
> If all an AjaxCheckBox subclass needs is to have the model updated, the call
> to onUpdate() is not necessary. In that case, the class can safely be
> concrete. In my case, I am calling setModel() on the AjaxCheckBox that is
> returned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
