On 3/4/08, Gabor Szokoli <[EMAIL PROTECTED]> wrote: > In the ajax debug window, I can only see the modalwindow form > submission, and no further activity.
Woops, this part was wrong. The <select> component was sent in the ajax response, but without the new choices added to the model by the modalwindow from submission. So we looked deeper, and we found the mistake we made: It has nothind to do with ajax. It was passing the model to the ListMultipleChoice: new ListMultipleChoice(wicketId, PropertyModel(parentsCompundPropertyModel, wicketId)) did the trick. With other components, this is equivalent to the wicketId-only constructor. Browsing the sources it seems to me that AbstractChoice breaks this convention: If you supply a model, that's your "choices" model. If you don't, your choices model is the empty list. I understand the reason (the choices model is only the secondary model), just wanted to point out the possible (and now actual) source of misunderstanding. Thanks for your help, sorry about the goosechase episode in the end. Gabor Szokoli --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
