This new scope is designed to fill a gap in the existing scopes available for JSF 2. ICEfaces 2 introduces a new custom scope called Window scope.

This behavior was configurable to allow for the more standard definition of request scope but was considered necessary at the time because the existing standard scopes (request, session, application, none) were not sufficient for supporting ICEfaces features like partial submit and Ajax Push. A request is not considered a new request unless it results in a new view so request-scoped beans would not be recreated until a new view was created. This means that Ajax requests that occur within an existing view are not treated by ICEfaces as new requests. In a nutshell, extended request scope refers to the behavior that a new request is only associated with a change in view. _EMPTY_FIELDS false īy default, ICEfaces 1.x operated under what was referred to as extended request scope. Add the following to the web.xml of you application:

If your application runs in compatibility mode and uses the ICEfaces 1.8 dynamic resource API directly or uses components that use the dynamic resource API ( OutputResource, DataExporter, HtmlGraphicImage, InputRichText), you must configure the CompatResourceServlet and servlet mapping to ensure that the resources are properly handled for JSF 2.

Persistent Faces Servlet .xmlhttp.PersistentFacesServlet 1 Blocking Servlet .xmlhttp.BlockingServlet 1 Persistent Faces Servlet *.iface Persistent Faces Servlet /xmlhttp/* Blocking Servlet /block/* When using JSTL with Facelets in JSF 2, use the following namespace in your.The tag and component are no longer required.However, if you do have it in your page, then it should be nested within the tag and not outside of it. Here are some of the things you may need to adjust as you move your applications from ICEfaces 1.8.x to ICEfaces 2: All development should be done in Facelets. In ICEfaces 2, JSP is no longer supported for creating pages. Existing applications that use Facelets can be migrated with little or no modifications to the pages. New applications must be developed in Facelets. The most popular of these is Facelets and it has now been adopted as the new standard page description language for JSF 2. In JSF 1.x, the standard mechanism for describing pages is JavaServer Pages (JSP), however, as the use and adoption of JSF increases, JSP is seen as a less than optimal solution for page development and alternatives were developed. Page Description Language - JSP and Facelets This section of the documentation outlines what the different parts of the compatibility layer are as well as noting areas of an application that may need to be modified or updated. To provide as smooth a migration as possible for developers that want to port their applications, ICEfaces 2 provides a compatibility layer to help reduce the resources required to move an application from ICEfaces 1.8.x to ICEfaces 2. ICEfaces 2 has been developed specifically to take advantage of the improvements, optimizations, and new features of JSF 2, however, developers with existing ICEfaces 1.x applications that want to move their applications to use ICEfaces 2 and JSF 2 want to do so with minimal disruption and effort.

Jsf icefaces developed by