I dug up the mountain and found this mouse:
There was a typo while building request string:
do you see it ?
else if (element.type == "checkbox" && element.checked == true)
datatosend += ( element.name + "=" + escape(element.value) + "&
");
No...? Look at the space after '&' and before the closing brackets :-)
-Piyush
----- Original Message -----
From: "Piyush Hari" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, November 10, 2006 4:26 PM
Subject: Re: Re: Re: Re: valueChangeListener of a selectBooleanCheckbox
When I remove the code that would submit the value each time it is checked
(check1=t) from the Core.js , the valueChangeListener gets called
properly. But, this is obviously not the right thing to do since the user
might need to submit a value.
-Piyush
----- Original Message -----
From: "Adam Winer" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, November 10, 2006 4:15 PM
Subject: Re: Re: Re: Re: valueChangeListener of a selectBooleanCheckbox
On 11/10/06, piyush hari <[EMAIL PROTECTED]> wrote:
Upon checking a check Box, getSubmittedValue() does not get called. Upon
unchecking it does get called.
That should be investigated.
HTTP request differs in t.o the attribute check1 (check1 being the
user-assigned ID of the checkBox). It does not get passed upon
unchecking.
It gets passed with a value 't' upon checking.
Upon checking:
check1=t
&org.apache.myfaces.trinidad.faces.FORM=_id1
&org.apache.myfaces.trinidad.faces.STATE=%2138234b14
&source=check1
&event=check1
&partialTargets=
&partial=true
Upon Unchecking:
org.apache.myfaces.trinidad.faces.FORM=_id1
&org.apache.myfaces.trinidad.faces.STATE=%2138234b14
&source=check1
&event=check1
&partialTargets=
&partial=true
Those look fine.
-- Adam
