Hey thanks!
this solved the validation problem but created another one:
1. When the user fills nothing in field1, uiField1.getValue() doesn't
return null, but returns an empty String object. I don't know if this was
intented.
2. When I attach a valueChangelistener to a field that the user didn't
change, it still triggers the valueChangeListener. The event.getOldValue()
returns null as should be but the event.getNewValue() returns an empty
string which isn't the same thing as null.
Greetings
Jan
On Wed, 25 May 2005 18:18:14 +0200, Sean Schofield
<[EMAIL PROTECTED]> wrote:
Jan,
I think Martin fixed this last night. Can you check the latest source
code (SVN or tonight's upcoming nightly build)?
sean
On 5/25/05, Martin Marinschek <[EMAIL PROTECTED]> wrote:
Another one. ;)
this is a known bug (or a feature ;).
good, it will be necessary to look into that very soon, I'll see if I
get around to do that tonight.
regards,
Martin
On 5/25/05, Jan Bols <[EMAIL PROTECTED]> wrote:
> I have a form with 2 fields field1 and field2. During validation
field2
> inspects the value of field1 for a null value:
> UIInput uiField1 = (UIInput)
toValidate.findComponent("field1");
> String field1Value = (String) uiField1.getValue();
> if (field1Value == null) {
> uiField1.setValid(false);
> message = "Error";
> context.addMessage(uiField1.getClientId(context), new
> FacesMessage(message));
> }
> The problem is that uiField1.getValue() returns the old value instead
of
> the updated value. This only happens when the user deletes the value
of
> field1. If the user specifies antoher (not null) value in field1
> uiField1.getValue() does return the correct new value.
>
> Am I doing something wrong? Is this a bug?
>
> Jan Bols
>
