dont know if we want to fix 1474136 because this means that we have to make a very special
setModelObject() that is there only for the 2 FormCompoent CheckGroup/ListMultiplyChoice
So that they can set the value without modelChanging/changed and the compare if equal..
Or we have to be able to do all the stuff that we do now in setModelObject also in subclasses
that means that somethings can't be hidden and must be protected.
And this is all so that we do a setModelObject with the same object that is already in the model
but to let the model know that it is changed/set.
1427212 Don't know if we need more testing for clustering. I did already some testing with 2 resin instances
But that was a while ago maybe we need to do it one more time before the final.
This bug shouldn;'t be closed anyway but moved to 2.0 so that we do it in 2.0 also again.
johan
On 4/23/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Here's our todo list.
1475128 Replace ${input} with ${label} in Application.properties
1475043 AbstractColumn constructor has Model as displayString param
1474813 Ajax ClassCast exception at AjaxFormSubmitBehavior
1474193 ClassCastException in AjaxSubmitButton
1474136 Setter for ListMultipleChoice with PropertyModel not called
1474092 onLoad contributed by Panel is not removed
1473355 BufferedWebResponse constructor should be public
1472044 check serialization errors
1471889 ValidationMessage Resource lookup doesn't work for FormInput
1458090 autolinking appends locale on 2nd+ renders
1438245 forminput datepicker picks illegal dates
1427855 example to display different usages of IFeedback
1427809 FIXME and TODO comments
1427212 Test clustering before 1.2 final
1424565 Create example document with repeaters
1424562 Create example document with panel components
1424559 Create example document with ajax handler
1364809 DatePicker doesn't work in opera
Are there things we can close already?
Martijn
--
Wicket 1.2 is coming! Write Ajax applications without touching _javascript_!
-- http://wicketframework.org
