This worked great but why is a separate call needed?
the Rerendering should find out the model value is null
and do the same as it did for the first rendering.
Is it due to the Javascript effect?
The second request would set the value to the first rendering
but after that, the my call back resets it to null and the rendering
kicks in in that order which would pick the null value as the secondchoice?
>but it is not just like it was after it has been created is it? it is
>currently holding a value from the request. anywho:
>
>secondchoiceSelected=null;
>secondchoicedropdownchoice.clearInput();
>
>and you will have what you want.
>
>-igor
>
>
>On Feb 4, 2008 7:36 PM, <[EMAIL PROTECTED]> wrote:
>> The following is the code sample
>>
>> class webpage
>> String secondchoiceSelected;
>>
>>
>> }
>> new Firstdropdownchoice( ){
>> onSelectionChange{
>> secondchoiceSelected = null;
>> }
>>
>>
>> I did set to null. This issue is that the displayed value is
>> the first item of the new list, instead of "Choose One", it is not
>> displaying the old secondVarSelected since I already set it to null.
>> Basically, when the dropdownchoice is redisplayed and is model is
>> null, it is supposed to display the same as the first created. It does
>> not appear this way.
>>
>>
>>
>>
>>
>> >whe the first is submitted you have to set the second one's model object
>to
>> >null
>> >
>> >-igor
>> >
>> >
>> >On Feb 4, 2008 4:59 PM, <[EMAIL PROTECTED]> wrote:
>> >> Hello:
>> >> I am using two dropdownchoices, after the first select, the second would
>get
>> >data on the fly using the first choice. The first round everything is
>fine
>> >with both displaying "Choose One" and selecting the first one set the
>correct
>> >second one list of choice with "Choose One" still displaying on the second
>so
>> >that one could click on it to pick the right one. After the first round, I
>> >select a different value in the first one, which resets correctly the
>second
>> >one' list as in the first round but strangely this time, the 'Choose One"
>> >display is gone in the second dropdownchoice. Instead it shows the first
>item
>> >of the new list. I used the wicket-examples sample code as basis and use
>> >getObject() to load the correct list when selection on the first changed.
>> >> Thanks
>> >
>> >---------------------------------------------------------------------
>> >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]
>>
>>
>
>---------------------------------------------------------------------
>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]
