Sorry for ignoring your post,
here the answer:
MyFaces 1.0.9 had a TCK compatibility bug with respect to setting
nulls back to the backend, instead of an empty string.
I still haven't checked though if a value change listener ought to be
fired in this case. I would suppose that not, but will need to check
the RI what it does in this case.
Fancy checking it out and open a jira issue if we don't do as the RI does?
regards,
Martin
On 9/26/05, Boris Klug <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I had the same problem. I figured out that we set most values to null,
> not to an empty String (""). After submitting the form, the value was an
> empty String, so the value changed and the events get fired.
>
> We changed the initial value to an empty String and now I no longer get
> the valueChangedEvents.
>
> See my posting here:
> http://www.mail-archive.com/users%40myfaces.apache.org/msg09062.html
>
> I asked there if this is the normal behaviour but got no answer.
>
>
>
> [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > I upgraded our app simply by replacing the jars of the 1.0.9 version
> > against the new ones (configuration changes have not been necessary).
> > Almost everything of the application works fine but:
> >
> > When a form is submitted, all methods which are registered as
> > valueChangeListener are called, even if the concerning UIInput has no
> > value or the value has not been changed.
> >
> > Since we have many valueChangeListeners on some pages and perform some
> > complex stuff in them, the business logic does not work any longer.
> >
> > Thanks fpr help,
> >
> > Daniel
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Trainings in English and German
