Further information: Ajax4jsf RichFaces originated from the Ajax4jsf framework which Alexander Smirnov designed and implemented. In March Exadel released the first version of what would become Ajax4jsf. While RichFaces provided out-of-the-box components a "component-centric" Ajax approach, where components do everything you need , Ajax4jsf provided page-wide Ajax support. Developers specify which parts of the page the server should process after some client-side user actions and which parts should be updated after processing.
|Published (Last):||13 October 2016|
|PDF File Size:||17.18 Mb|
|ePub File Size:||6.97 Mb|
|Price:||Free* [*Free Regsitration Required]|
This project is read only now. Read more. Last modified by michpetrov on Feb 12, AM. All resources are staying where they are; we will still host the documentation, downloads and the RichFaces Showcase. What will happen if a serious bug or security issue is discovered in the future? There will be no patches after the end of support. In case of discovering a serious issue you will have to develop a patch yourself or switch to another framework.
Can we keep using RichFaces or should we switch to another framework? Apart from the core codebase upgrading third-party libraries jQuery, CKEditor, … is fairly straightforward so you can keep your project up-to-date.
However if you encounter any bugs you will have to patch the source code yourself or switch to another framework. Do you have a recommendation for a framework we should switch to? There is no direct replacement for RichFaces so you will need to change your code to make it work with the new framework. You can choose from any JSF-based frameworks that are still active.