I could actually "hack" this feature by adding an AjaxButton onto the page which has defaultFormProcessing=false and then hide that button using css/style and always invoke that button when a checkbox is clicked. But it would be betterto just make sure Wicket supports such events for FormComponents.
::: > Maybe a conversion error that prohibits updating the model? I do not want to update the model. I want "defaultFormProcessing=false" with the particular ajax event. > In a way, yes, but sometimes purely client-side stuff can be > easier purely on the client-side. The functionality is already in Wicket because wantOnSelectionChangedNotifications=true works (non-ajax). If it does not yet exist for Ajax, I would like someone to guide me and I could maybe code it myself. ** Martin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
