![]() ICEfaces 2 core has no 3rd-party library dependencies outside of those libraries specified in the JEE 6 "Web Profile". This makes it even quicker and easier to add ICEfaces to your JSF application, and greatly reduces the possibility of lost productivity due to minor configuration errors. The ICEfaces-specific servlets and many of the configuration parameters in ICEfaces 1.x are no longer necessary with ICEfaces 2. While JSF 2 simplifies configuration by leveraging annotations, ICEfaces also streamlines configuration in several areas. In addition to enhancing the basic Ajax features provided by JSF 2, ICEfaces extends a client-side API for monitoring interesting events that occur on the client, such as form submission, event callbacks, and Ajax Push connection monitoring. The PortletFaces Bridge is tested and shipped with the ICEfaces 2 distribution and can be used to develop portlet applications with ICEfaces. The portlet bridge spec technically applies to JSF 1.2, but the PortletFaces version has been adapted to support JSF 2. Portlet support in ICEfaces 2 is provided by the PortletFaces Bridge, an implementation of the JSR 329: Portlet 2.0 Bridge for JSF. Each Resource is registered in a specified scope (Application, Session, View, Flash, or Window) so that the resource can be garbage collected when the scope expires. The ResourceRegistry allows an application to register instances at run time. Specifically, the annotations allow you to control the behavior of view-scoped beans across repeated navigation to the same view, and during view disposal. While View scope is a welcome addition for managing the lifecycle of beans, the behavior of View scope may not be intuitive in certain scenarios. Bean ManagementĪnnotations are provided that adjust the behavior of View-scoped beans. The custom Window scope is designed to fill a gap in the existing scopes available for JSF 2.0, as it exists for the life of a browser window or tab, including surviving reloads and refreshes. New Ajax Push APIs make it simpler than ever to add collaborative features to your application. Any state change in the application can instantaneously push updates to other users of the application that need to be informed. From there the D2D mechanism determines the exact set of incremental page changes required in response to the Single Submit.Ījax Push enables real-time, multi-user collaboration in your JSF application. The JSF lifecycle executes on just that single component, and then the entire render phase is executed. ![]() Single Submit enables all components to automatically submit themselves base on user interaction.Simply adding the ICEfaces 2 library to an existing JSF 2 application will provide dynamic partial-page-updates for all compliant components, without the need to specify the JSF component in your pages. Each time the JSF lifecycle runs, a DOM comparison is done, and if there are any changes, a concise set of page updates are sent back to the client to be applied to the page. Direct-to-DOM Rendering (D2D) renders component markup to a server-side DOM that reflects the current client view.ICEfaces 2 includes several innovative features that cumulatively result in Automatic Ajax, completely eliminating the need for developers to wire page updates together using standard JSF tags. The following framework enhancements extend the capabilities of standard JSF 2: Automatic Ajax ![]() ICEfaces 2 provides some key feature enhancements over JSF 2, while inheriting all the new features available in JSF 2. ICEfaces 2.0 is available for download in the following formats: ![]() These Release Notes include the following sections: ICEfaces 2.0.0 is the official release of the next-generation of ICEfaces, designed for JSF 2.0. Cannot resolve external resource into attachment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |