the component remembers its submitted value and tries to rerender
itself using that. this value is cleared when the form is processed,
but remember you havent processed the form - you only processed the
first dropdownchoice.
-igor
On Feb 5, 2008 2:35 AM, <[EMAIL PROTECTED]> wrote:
> This worked
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
Thanks very much.
>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 P
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 followi
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 O
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 everythin
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 display
