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

Version 3
    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
    ajaxValidatorvalidatorClient validation feature added. Processes both JSR-303 and standard validators. Uses the same ajax validation as for 3.3.x in case where client validation not applicable. [demo]
    beanValidatorremovedNot required as standartized in JSF.
    graphValidatorgraphValidatorWorks in the same way. Important: uses clonning validated bean in order to validate at proper phase. So if  want to validate at proces_validations - implement Clonneable in your object and add public clone() method. [demo]
    messagemessage

    Same Ajax auto update feature.

    Important! Icons usage changed to just CSS. Summary and Details became separate elements so skinning improved. [reference]

    Added with the client side updates support and used by Client Side Validation.

    messagesmessages

    Same Ajax auto update feature. Icons usage changed to just CSS. Layouts definitions also changed to just CSS usage. Summary and Details became separate elements so skinning improved.

    Added with the client side updates support and used by Client Side Validation.

    n/a

    notify

    notifyMessage

    notifyMessages

    notifyStack

    The notify components are new with RichFaces 4