I'm not sure how you're using the fireAjaxTransaction function of JSF
Extensions. However, this is typically used to render a component
server-side and completely replace previously existing HTML elements.
The Woodstock refresh feature also uses fireAjaxTransaction, but only to
obtain new widget properties. The component is not rendered again, but
selectively updated client-side. If you're not using the Woodstock
refresh feature, I'm not certain we can help you. However, perhaps you
can explain how you're updating widgets via fireAjaxTransaction? You
might also try your question on users_at_jsf-extensions.dev.java.net.
Dan
Rasha 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
>