Chapter 4. The RichFaces Migration Issues 3.1.x
Issues with upgrading from previous versions
This section covers issues you can encounter upgrading to RichFaces 3.2.0 from previous versions.
<rich:calendar> and "ondateselected" event problem
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.
RichFaces Forum [http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132914]
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.
Events firing sequence was changed.
You need "onchanged" event to be fired after any change which causes input to be updated, both date and time.
"ondateselected" event is fired after a date is selected in popup
"ontimechanged" event is fired after new time is selected.
Paired <rich:datascroller> components do not work
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