Your component keeps it's "validated" attribute. Either you clear the
client field (but do not remove it!) in form -> your validator gets a
null/empty string, depending on your converter, either you change the
"rendered" attribute of component (it will not get validated nor pushed
to backing bean)
Jonathan Martin a écrit :
Hi,
I have a configured a validation class in the faces-config and have an
issue I would like to solve.
I have a scenario where I am posting a form with a field, which is
validated against when populated. If invalid data is put into the
field I am returned to the originating page and an appropriate error
message is displayed, so far so good. I have a condition where I can
now send the form “validly” in which the originally offending field is
not re-sent / posted on the request. But the same validator fails with
the previous data which has not been re-sent.
I’m presuming this is being cached inside the faces context and not
being cleared/updated as the data/parameter is not on the request and
therefore validated against again.
Can anyone tell me if myfaces can be configured to clear any non
re-posted parameters inside its cache if this is what is happening?
Thanks in Advance,
Jonathan.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
