At the moment there is a problem with
it, because of the canged behavior of the UIInput component (through MYFACES-277).
Now it does not make much sense to use
it, because all not validated fields will lose their value and the user
has to reenter all the data.
My opinion is that this new
Thanks for pointing that out. I'm now watching MYFACES-277. I'm
currently using the immediate=true methodology, but I'm convinced that
a separate form is the best solution for my use case.
On 8/8/05, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
At the moment there is a problem with it,
I had a similar problem. I use UIInput
components with NO value binding. Instead the components have a valueChangedListern
(function) of a bean. So the values are added there internally.
Setting immediate=true on
the input components helps, but if you have serveral parts
of a form, e.g. a second
Yes that might be helpful. Can you make
the code available? Thanks!
-
Eric Kelm
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Friday, August 05, 2005 2:41
AM
To: users@myfaces.apache.org
Subject: Antwort: Re: Problem with
commandButton and required
4 matches
Mail list logo
