RichFaces Migration Guide. 3.3.x - 4.x Migration - Components migration - Rich Input 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
    calendarcalendar

    Not changed. Some client API methods were renaimed so follow reference for that changes.

    Markup customization using Facets/client substitutions not implemented for Final and will be redesigned. Only header/footer/optionaHeade/optionalFooter available.

    colorPickerno implemented for Final
    n/a
    comboBoxsee suggestionBoxmerged with suggestionBox component
    editoreditor
    RichFaces 4 is based on the CKeditor
    fileUploadfileUpload

    not changed. Not implemented functionality in Final:

    • JS API
    • auto upload / auto clear the list
    • flash support
    inplaceInputinplaceInput

    Works in the same way. Special handlers like onviewactivated were removed and more convinient and standard onchange added.

    Controls redefinition using facets - not implemented.

    inplaceSelectinplaceSelectthe same as for inplaceInput.
    inputNumberSliderinputNumberSliderNot changed.
    inputNumberSpinnerinputNumberSpinnerNot changed.
    suggestionBoxautocomplete

    Unified version of suggestionBox and comboBox from 3.3.x. Could works in 4 different modes:

    • client(like combo),
    • ajax(like SB)
    • cachedAjax(ajax but with less requests only when prefix updated)
    • lazyClient(single load of the suggestions but only after first time needed)

    Uses valueBinding to suggestions(autocompleteList attribute) or method binding(autocompleteMethod attribute) to service method which should returns them.

     

    Component is UIInput, so objectSelection is not implemented and most possible not going to be there. See select component.

    -select

    New component which is UISelectOne based but allows dyrect typing as for autocomplete(prev suggestionBox). Designed for those who needs label/value selection from 3.3.x combobox.

     

    Planned to be added with:

    • additional data columns support
    • ajax loading similar to autocomplete.