X hits on this document

63 views

0 shares

0 downloads

0 comments

10 / 20

Chapter 4. The RichFaces Migration Issues 3.1.x

  • -

    3.2.0

    • 4.2.

      Issues with upgrading from previous versions

This section covers issues you can encounter upgrading to RichFaces 3.2.0 from previous versions.

      • 4.2.1.

        <rich:calendar> and "ondateselected" event problem

        • 4.2.1.1.

          Description

The <rich:calendar> date selected event is fired before input update.

If time and apply elements are added to the calendar, "ondateselected" gets fired when a date is

selected but before it's updated in input. Now we have three events instead of one. But it causes compatibility problem because this event was used by customers to save selected value via Ajax.

        • 4.2.1.2.

          Links

          • RichFaces Forum [http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132914]

        • 4.2.1.3.

          How to reproduce

The described above problem occurs when <a4j:support> is put inside <rich:calendar>. If the "event" property is set to "ondateselected" previous value of the <rich:calendar> is stored after selection.

4.2.1.4. Causes

Events firing sequence was changed.

4.2.1.5. Workarounds

You need "onchanged" event to be fired after any change which causes input to be updated, both date and time.

Note, that

  • "ondateselected" event is fired after a date is selected in popup

  • "ontimechanged" event is fired after new time is selected.

      • 4.2.2.

        Paired <rich:datascroller> components do not work

        • 4.2.2.1.

          Description

Two <rich:datascroller> components bound to the same table aren't synchronized. Having two <rich:datascroller>components on a page, session-scoped beans saves the data for only

11

Document info
Document views63
Page views63
Page last viewedThu Dec 08 00:45:59 UTC 2016
Pages20
Paragraphs460
Words3352

Comments