Yes that might be helpful. Can you make
the code available? Thanks!
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Friday, August 05, 2005 2:41
AM
To: [email protected]
Subject: Antwort: Re: Problem with
commandButton and required form fields
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 add button and input fields
you are getting into troubles again.
One
solution is to split the form. But you would lose all other entered values and
if client state saving is on you get much overhead.
To
solve the validation issue I have created a component to simulate a partial form
submit (or better partial validation). With this component I can divide the
form ito serveral "parts" where the validation and update model phase
is only invoked on the components if a command component was clicked of this
part.
Maybe
this would help you, too?
|
- RE: Antwort: Re: Problem with commandButton and required... Eric Kelm
-
