More info: validation failure is not a necessary condition.
I have a tr:selectOneChoice, which allows for choosing either a boolean
or a number. Selection renders (through PPR from autoSubmit) either a
tr:inputText or a tr:selectBooleanCheckbox.
Now I select "number", enter a number and add it to a list (via PPR),
then I select "boolean", check it and add it to the list.
At this point, I noticed that in function _multiValidate the number
validator is called through decimalParse, using the value "true" as
current string to validate.
It seems that switching from inputText to selectBooleanCheckbox using
PPR did not update the current validator.
-- Renzo
Renzo Tomaselli wrote:
Hi, while using Trinidad v. 1.0.3, I forced a client-side validation
error by entering an invalid short number.
At the next PPR, I got a js error on Firebug:
"e.getFacesMessage() is not a function"
at line 6199 in Common1_0_3.js (in function _multiValidate). The
involved line appears to be in a catch such as:
catch (e)
{
converterError = true; // Populate the failureMap with the
current error
inputFailures[inputFailures.length] = e.getFacesMessage();
}
where "e" contains "a0.indexOf is not a function".
-- Renzo
