September 30th, 2011
These Release Notes include the following sections:
- About This Release
- Notable Changes
- Supported Platforms
- Known Issues
ICEfaces 2.1 Beta is a pre-release build of ICEfaces 2.1 and is not suitable for production deployments.
ICEfaces 2.1 Beta is available for download in the following formats:
- This release has been tested with Mojarra JSF 2.1.3, and includes the JSF 2.1.3 library in the download bundles.
- This release has been tested with Apache MyFaces JSF 2.1.3, and includes the MyFaces 2.1.3 libraries in the download bundles.
- See the Known Issues section for details on remaining issues with MyFaces support.
- Custom Update Support
- The ICEfaces Direct-to-DOM rendering engine has been enhanced to support partial component tree rendering that may consist of regular DOM-diffed regions combined with new sub-component custom update regions that are excluded from DOM differencing. This feature enabled richer ACE component interactions and efficiencies for specific use-cases.
- Window Scope
- Support for @PostConstruct and @PreDestroy annotations has been added to the ICEfaces custom Window scope.
- Delta Submit Improvements
- The Delta Submit implementation has been completely reworked to improve efficiency and robustness.
- New messagePersistence Configurability
- New configuration parameter and iceore:config attribute have been added to support configuration of ICEfaces "intelligent message caching" feature.
- Alternatively, a new may be used to enable/disable message caching within a page.
- Several aspects of the core framework have been optimized to reduce execution time and/or Java heap consumption.
- New <icecore:push group="chat"> Tag
- A new <icecore:push group=""> tag has been added to make push group registration easier.
- Multiple occurrences of this component within a view can be used to add the current view to different groups.
- Removal of expired views from the group currently relies on the automatic clean-up of the groups themselves.
- Automated ICEpush Setup/Teardown
- By default, ICEpush will now automatically setup and teardown it's blocking connection on a per-page basis, depending on whether or not any ICEPush groups are active on the page.
- Previously, ICEpush was lazily initialized, but not actively teared-down if a once active push group became inactive on the page.
- New lazyPush Configurability
- A new configuration parameter has been added to disable the automated lazy initialization and teardown of ICEpush, forcing ICEpush to keep its blocking connection active at all times.
- There is also an attribute for the ice:config tag that allows page-level configuration. This take precedence over the context parameter setting.
- Improved support for auto-scrolling when dragging a panelGroup inside a scrollable <DIV>.
- The ice:dataExporter now uses converters when exporting data.
- Added "partialSubmit" attribute to the ice:selectInputText component.
- Added "escape" attribute to ice:message and ice:messages.
- Added tabIndex attribute to ice:dataPaginator, ice:rowSelector/ice:datatable, and ice:panelCollapsible.
- New Comp-Suite Sample Application
- An all-new ICEfaces Component Suite (comp-suite) sample application is introduced in this release.
- Currently features preliminary demonstrations for the new ACE components.
- Comp-Suite demo is in "preview" status and does not reflect final styling and behavior.
- ACE-Showcase Removed
- The original ace-showcase sample application has been removed from ICEfaces 2.1, replaced by the new comp-suite application.
- NetBeans 7
- This release provides a new IDE integration for NetBeans 7.1.
- Eclipse 3.7
- Eclipse 3.7 is also supported.
For a complete list of all changes in this release, see the related JIRA Change Log.
The following section describes the most commonly encountered known issues with this release:
- JSPs are not supported by ICEfaces 2.0 - use Facelets.
- It is required to specify "h:head" and "h:body" tags in your ICEfaces application pages.
- The Delta-Submit function does not support cases where an Ajax DOM update in the browser dynamically introduces new form elements into the DOM that were not part of the form when the page was originally loaded. In order to use Delta-Submit successfully all form elements / components must be present on the page at the time the page is loaded.
- Due to an apparent bug in the Sun Mojarra JSF 2 runtime library, component binding is not reliable when used within a View scope.
- The recommended workaround is to use the ICEfaces "Window" or JSF "Session" scopes instead if component-binding is required. Alternatively, applications can be modified to avoid the requirement for using component-binding in View scope by using techniques similar to that used in the Data Paginator demo section of Compatible Component Showcase application. For details, see ICE-5226.
- Note that the Mojarra JSF 2.1.0-2.1.2 releases have several serious issues that may impact your project:
- A bug that prevents it from supporting bean-annotation on non-Glassfish 3.1 application servers and servlet containers.
- Several bugs that prevent the IE9 browser from working properly with JSF-ajax operations.
- Partial State Saving bugs that might prevent the use of Partial State Saving in your application.
- This release of ICEfaces includes the Mojarra JSF 2.1.3 release libraries which resolves the known issues noted above.
- 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.
- 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:
- See http://jira.icefaces.org/browse/ICE-6138 for more information.
- Tomcat 6.0
- In some cases, when running Tomcat on Windows, undeploying an ICEfaces 2 compatible application (i.e. that includes the icefaces-compat.jar) can cause an exception. See http://jira.icefaces.org/browse/ICE-5222 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:
- Glassfish 3 / JBoss 6 (JEE 6 Platforms)
- It is necessary to have Mojarra JSF 2.1.0-FCS or greater (2.1.3 is recommended) installed. This may require updating the JSF Mojarra runtime libraries in Glassfish 3 or JBoss 6, depending on which JSF version is currently installed.
Open source community support is available at http://www.icefaces.org.
The ICEfaces community forums are available for questions, comments, or general discussions regarding ICEfaces 2.