ICEfaces 3.1.0.BETA1 Release Notes

Table of Contents

ICEfaces 3.1.0.BETA1 Release Notes

May 18th, 2012


About This Release

ICEfaces 3.1.0.BETA1 is a preview release of ICEfaces 3.1.0 and is not suitable for production use.


ICEfaces is available for download in the following formats:

What's New in 3.1.0.BETA1?

ACE Components

New Components:

  • ace:autoCompleteEntry - features built-in and lazy-loaded suggestion list filtering.
  • ace:chart - provides interactive client-side rendered dynamic charts without browser plugins.
  • ace:list & ace:listControl - single ordered column list, dual column list, or n-column list controls.
  • ace:menuSeparator - Group your menuItems into logical sets
  • ace:multiColumnMenu - Adds "mega-menu" style submenus to ace:menuBar and ace:contextMenu.
  • ace:richTextEntry - Leverages the industry-leading CKEditor rich text library.
  • ace:textEntry - features integrated label rendering (incl. Inplace/InField labels), and required/optional indicators and styling.

Updated & Enhanced Components:

  • 3rd Party JavaScript Libraries
    • Updated jQuery to v1.7.1, jQuery UI to v1.8.18, and Wijmo to v2.0.5
    • Optimized key-event listeners based on new jQuery 1.7 techniques for improved performance on older/slower browsers.
  • ace:dateTimeEntry - New "tabindex" attribute.
  • ace:dataTable
    • Can now select ranges of rows via shift(key)-click.
    • Added support for setting "maxHeight" on scrollable dataTable (to keep footer nested below last row)
    • Now indents the expansion toggle control in nested row expansion scenarios.
    • Added support for displaying unique styling for cases where row selector is hovered over a selected row
  • ace:notificationPanel - Added new "visible" attribute and "onDisplay" event listener
  • ace:tooltip - Added capability to interact with the contents of the tooltip (tooltip doesn't close while mouse hovered over it).

ICE Components

  • ice:dataExporter
    • The ice:dataExporter component now supports PDF formatted exports.
      • This feature requires that the itext-2.1.7.jar be included in the application classpath (not provided in the ICEfaces bundle due to license restrictions).

Core Framework

  • New icecore:navigationNotifier component
  • New icecore:redirect component
  • New icecore:refresh component
    • Provides support for periodic page refreshes triggered from the client.
    • Leverages ICEfaces Ajax-Push architecture for optimal simplicity and performance.
    • See the Wiki Topic for details.
  • JavaScript and CSS Resource GZIP Compression Changes
    • ICEfaces no longer performs GZIP compression on CSS (.css) and JavaScript (.js) resource files (by default). It is recommended that GZIP compression be configured and performed by the application server or web proxy server.
    • See the new Wiki Topic for details and server configuration resources.
  • icecore:config configuration settings are now propagated into included xhtmls.
  • blockUIOnSubmit - It is now possible to customize the blockUIOnSubmit overlay styling via the new "ice-blockui-overlay" CSS styleclass.
  • Default Status Dialogs - It is now possible to customize the standard ICEfaces status dialog overlay styling via the new "ice-status-indicator-overlay" CSS styleclass.

Samples & Tutorials

  • ICEfaces Showcase Sample Application
    • New preliminary demos have been added to illustrate key features of the new ACE components.

IDE Integrations

  • NetBeans 7.1
    • This release provides an updated IDE integrations for NetBeans 7.1
  • Eclipse 3.6, 3.7, 4.2-M7
    • This release provides an updated IDE integration for Eclipse 3.6/3.7/4.2-M7.
Change Log
For a complete list of all changes in this release, see the related JIRA Change Log.

Migration Guide

An ICEfaces 2 to ICEfaces 3 Migration Guide is available for those wishing to migrate their existing ICEaces 2.x applications to ICEfaces 3.0.

Supported Platforms

JSF Runtimes

  • Oracle Mojarra JSF 2.1.3+ (2.1.6 is included).
  • Apache MyFaces JSF 2.1.6 (included)


  • Chrome 19
  • Firefox 3.6 - 12
  • IE 6, IE 7, IE 8, IE 9
  • Safari 5

Mobile Browsers

  • Apple iOS Safari
  • Google Android Chrome
  • RIM BlackBerry OS6 WebKit Browser
A subset of component functionality, such as those requiring mouse-drag operations, are not currently supported on mobile devices with touch-screen interfaces.

Application Servers

  • Apache Tomcat 6, 7
  • Oracle Glassfish v3.0, 3.1
  • RedHat JBoss AS 5, 6, 7

Portal Containers

  • Apache Pluto 2.0.3
  • Liferay Portal 5, 6

(All portlet deployments require the PortletFaces Bridge library. Note that the version of the PortletFaces Bridge that is currently shipped with ICEfaces includes fixes that aren't available with the generally released version. Ensure you use the copy of the library that ships with ICEfaces for all of your ICEfaces portlet deployments.)

Known Issues

The following section describes the most commonly encountered known issues with this release:


  • JSPs are not supported by ICEfaces 3 - use Facelets.
  • It is required to specify "h:head" and "h:body" tags in your ICEfaces application pages.
  • Applications must avoid the use of "javascript: void(0)" in browser DOM event handlers as this technique causes the "onBeforeOnload" event handler to be called in IE, which results in the ICEfaces bridges shutting down (thinking that the page is being navigated away from).

1.8.x Compatibility

  • In ICEfaces 2+, the "Request" scope is the "standard" JSF Request scope, and not the "Extended" Request scope that was the default in ICEfaces 1.x. This change may result in failures for ICEfaces 1.x applications that relied on the Extended Request Scope behavior that are being moved to ICEfaces 2.0. The workaround for this issue is to adopt one of "View", "Window", or "Session" scopes in JSF/ICEfaces 2+ instead.

Mojarra JSF

  • This release includes the Mojarra JSF 2.1.6 runtime libraries.
    Note that Mojarra 2.1.4 introduced a dependency on Servlet 3.0 APIs, as a result, it cannot be used on older JEE5 application servers. Mojarra 2.1.3, or Apache MyFaces 2.1.6 should be used in on older JEE5 servers instead.
  • Note that the Mojarra JSF releases prior to 2.1.3 have several serious issues that may impact your project and are not recommended.
  • When running a JSF application in JSF2 PROJECT_STAGE="Development" mode (which is the default setting for all ICEfaces sample applications), you may see the follow warning appear at the bottom of the page: "Form component needs to have a UIForm in its ancestry.".
    • This issue is caused by a bug in Mojarra JSF, a suggested work-around is to set the JSF2 PROJECT_STAGE="Production" in the web.xml file.

MyFaces JSF

  • Portal Detection
    • MyFaces 2.1.6 has a defect that prevents proper detection of Portlet 2.0 spec. portal containers.
    • To work-around this issue, this release includes a patched MyFaces 2.1.6 library that resolves this issue (See details).
    • It is anticipated that this issue will be resolved in a future MyFaces JSF official release.
  • ace:dataTable w/ Row Expansion
    • An issue exists that prevents the use of the ace:dataTable with Row Expansion that contains editable components, on MyFaces only. At this time, Row Expansion can be used with none-editable components-only when running on MyFaces.


  • WebKit (Safari and Chrome)
    • The WebKit-based browsers (Google Chrome and Apple Safari) request content-type "application/xhtml+xml" by default, which is different from virtually all other browsers. In cases where the application page doesn't set the contentType explicitly this can result in these browsers defaulting to a strict XHTML rendering mode, which can cause some unexpected styling and layout issues. In order to have WebKit-based browsers render markup consistently with other browsers, you must specify the content-type in the view tag on each page:
      <f:view contentType="text/html">
    • See for more information.

Application Servers

  • Tomcat 6.0
    • In some cases, when running Tomcat on Windows, undeploying an ICEfaces compatible application (i.e. that includes the icefaces-compat.jar) can cause an exception. See for additional information about this issue. To prevent this, include a context.xml file with your application that includes the following Context attributes to prevent jar and resource locking:
      <Context antiJarLocking="true" antiResourceLocking="true"/>
  • Glassfish 3 / JBoss 6, 7 (JEE 6 Platforms)
    • It is required to have Mojarra JSF 2.1.3+ installed. This may require updating the JSF Mojarra runtime libraries in Glassfish 3 or JBoss 6/7, depending on which JSF version is currently installed.

Portal Containers

  • Liferay 5
    • Using the ACE Components with Liferay 5 can result in CSS styling conflicts between the Liferay themes and the ACE Component theme, as they both utilize the jQuery ThemeRoller styling scheme. It may be necessary to customize the themes to avoid conflicts when using the ACE components with Liferay 5. See the Custom ACE Styles for Liferay Portal Wiki topic for details.


Open source community support is available at

The ICEfaces Community Forums are available for questions, comments, or general discussions regarding ICEfaces.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

© Copyright 2021 ICEsoft Technologies Canada Corp.