RichFaces Migration Guide. 3.3.x - 4.x Migration - Components migration - Rich Miscellaneous Components

IMPORTANTThat document is under continous development. It's published in order you to have the fastest access to all the new info posted there even considering that document itself will be extended more in the same time. So please be patient, and do not forget leave your feedback and requests for additional information at RichFaces Space Forum. We could do it really great together!

Only component high-level changes and component-specific functionality removal/changes mentioned there. For common attributes names changes follow the [Rich components standartized attributes| link ]

 

RichFaces 3.3.3RichFaces 4.xChanges
componentControlcomponentControl

works the same.

effectno implemented for Final

jQuery jQueryworks the same. added with additional handler bindings features.
gmapnot implemented for Final
going to be reviewed and added with new tags for declarative definitions of points and so on.
hotKeyhotKey (as of 4.2)works the same.
insertnot implemented for Finalalready available as custom component at richfaces-showcase application.
messagemessagesee [validation components | link]
messagesmessagessee [validation components | link]
layout componentsnot implemented for Finalgoing to be reviewed. maybe will change Yahoo base.
pagenot implemented for Finalto be unified with former a4j:page.
state apinot implemented for Final

currently not going to be implemented.

virtualEarthnot implemented for Final
-hashParamnew parameter tag which allows grouping of f: and a4j: parameters into hash parameter for use at client side calls with componentControl.