I understand what you're saying but actually it's not an empty String I'm
getting but really the "x" caracter when I clean the textField.
That's so odd and I just found out it's an issue with JSF-Extensions.
There's a patch for it.
Thanks anyway.
On Dec 13, 2007 12:12 PM, Rasha <rasha.abdallah_at_murex.com> wrote:
>
> Well if your textfield is bound to a backing bean, the behavior will
> depend
> on that backing bean.
> For example:
> if you have a textfield where text="#{myBackingBean.someIntValue} then
> even
> if you clear the text, it will send the default value which is 0.
> Or if you have text="${myBackingbean.someDateValue}" then even if you
> clear
> the text, the default (today) will be sent.
> So this is not related to ajax, this is a pure component behavior when
> your
> data is bound to backing beans.
> PS: I don't think that "null" can ever be sent. It always some default. In
> the case of string, it's an empty string.
>
>
>
> Lking wrote:
> >
> > I'm with fireAjaxTransaction. I just started with it because I need more
> > than one component having it's values updated and Table is one of those
> > components. I was waiting for Table2 for this year but I just saw they
> are
> > planning now for May 2008 :(
> >
> > I'm with another issue right now that if I set an onChange event and
> clear
> > the textField it will send an "x" value instead of "null". Did you have
> > this
> > kind of issue?
> >
> >
> > regards.
> >
> >
> >
> > On Dec 13, 2007 11:40 AM, Rasha <rasha.abdallah_at_murex.com> wrote:
> >
> >>
> >> Hello Lking,
> >> not really.
> >> I reverted to using build 14 because the way build 15 is rendering its
> >> component is definitely not user friendly.
> >> Are you using fireAjaxTransaction or refresh() function ?
> >>
> >>
> >> Lking wrote:
> >> >
> >> > Rasha,
> >> >
> >> > I noticed the same issue.
> >> > Did you figure it out what's going on?
> >> >
> >> > thanks.
> >> >
> >> > On Dec 7, 2007 12:07 PM, Rasha <rasha.abdallah_at_murex.com> wrote:
> >> >
> >> >>
> >> >> Hello,
> >> >> I just upgraded to build 15, and I noticed a difference in the
> >> behavior
> >> >> of
> >> >> components when refreshing asynchroneously the components.
> >> >> In build 15, the components being refreshed disappear for few
> seconds
> >> >> from
> >> >> the page and then are redrawn, which is noticeable by the user, and
> we
> >> do
> >> >> not want this behavior.
> >> >> In build 14, the components being refreshed do not disappear, and
> for
> >> the
> >> >> end user it seems that only the text values have changed. Which is
> the
> >> >> correct behavior.
> >> >>
> >> >> Note that I am using fireAjaxTransaction method to aynchroneously
> >> submit
> >> >> and
> >> >> refresh my components. And not refresh() and submit() functions.
> >> >>
> >> >> Is there any particular reason for this difference in the behavior,
> >> and
> >> >> if
> >> >> so, is there a way we can make components behave as in build 14?
> >> >>
> >> >> Thanks
> >> >> Rasha
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://www.nabble.com/Asynchroneous-Refresh%3A-different-behavior-between-build-14-and-build-15-tf4962176.html#a14212797
> >> >> Sent from the Project Woodstock - Users mailing list archive at
> >> >> Nabble.com
> >> >> .
> >> >>
> >> >>
> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> >> >> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
> >> >>
> >> >>
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Asynchroneous-Refresh%3A-different-behavior-between-build-14-and-build-15-tp14212797p14316201.html
> >> Sent from the Project Woodstock - Users mailing list archive at
> >> Nabble.com
> >> .
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> >> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Asynchroneous-Refresh%3A-different-behavior-between-build-14-and-build-15-tp14212797p14316769.html
> Sent from the Project Woodstock - Users mailing list archive at Nabble.com
> .
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>
>