RichFaces 4.0 Final Released - 30/march/2011

Discussions

News: RichFaces 4.0 Final Released - 30/march/2011

  1. RichFaces 4.0 Final Released - 30/march/2011 (4 messages)

    The RichFaces project is an advanced UI component framework for easily integrating Ajax capabilities into business applications using JSF.  

    RichFaces 3 lead from the front with integrated Ajax support for JSF 1 and provided over 100 fully Ajax enabled UI components.  Several of the innovations from RichFaces 3 have been incorporated in the JSF 2 standards for all to benefit from.


    RichFaces 4 once again goes beyond simply supporting JavaServer Faces (JSF) 2.  It has extended multiple areas of JSF, including usability, performance tuning, dynamic resources, skinning, and component development.  This allows users to take full advantage of all the productivity enhancements of JSF 2.  

    • A full set of AJAX enabled components in two libraries
      • a4j: page centric AJAX controls
      • rich: self contained, ready to use components
    • Client-side validation, expanding JSR 303 Bean Validation all the way to the browser.
    • Advanced queueing to match the high performance requirements of real world enterprise applications.
    • Push component upgrades including JavaMessaging Service (JMS) integrations, and various transport mechanisms based on browser support.
    • Our own Component Development Kit (CDK).
    • Comprehensive documentation covering development best practices, and component details.
    • Detailed and automated testing facilities for components, actions, listeners, and pages.
    • Broad cross-browser support
    • Large and active community at its foundation!!

    http://www.jboss.org/richfaces

  2. Wow! FINALLY! :D

  3. So is Seam3 (2 days later).

  4. I for one. Could care less[ Go to top ]

    Get on board the Flex 4/J2EE stream. If you're interested in user experience acceptance. I'm not sure why anyone would bother with anything else.

  5. I for one. Could care less[ Go to top ]

    Get on board the Flex 4/J2EE stream. If you're interested in user experience acceptance. I'm not sure why anyone would bother with anything else.

    Because this "anything else" is in general better, simpler and has more support throughout the industry?