ICEfaces EE 4.3.0.GA_P01 Release Notes
June 19th, 2019
About This Release
ICEfaces EE 4.3.0.GA_P01 is a certified ICEfaces Enterprise Edition maintenance patch release.
ICEfaces EE is available in both binary and source download bundles from the www.icesoft.org download page.
Changes in EE 4.3.0.GA_P01
Additional Platform Support
This release has been certified on the following additional Java runtimes:
- JIRA - Using a filter facet on a sortable column triggers unwanted sorting.
- JIRA - Fixed a regression introduced in EE 4.3.0.GA that could cause rendering glitches when nesting ace:tabSet components.
- JIRA - Apply "disabled" styling when the component is disabled.
- JIRA - A fix for a serious issue when using Chrome v73.0.3683.103 with an ICEfaces application that uses Window-scoped beans. Chrome v73.0.3683.103 introduced a new limitation that interferes with ICEfaces ability to notify the server when a browser tab or window is closed. This causes unexpected issues when using Window-scoped beans and may result in frequent "Concurrent view exceeded" exceptions.
ICEfaces Enterprise Edition includes a suite of enterprise software and documentation that will enhance your ICEfaces project from development, through testing and deployment. In addition to high quality certified software and tools, ICEfaces EE includes direct access to the extensive knowledge and expertise of our technical team.
ICEfaces-EE provides the following additional exclusive features in addition to all of the features available in ICEfaces:
ICEfaces EE has been certified against a wide-range of supported commercial and open-source application servers, portal-containers, and 3rd-party frameworks. See the Supported Platforms section for details.
Enterprise Push Server (EPS)
The [Enterprise Push Server] extends the standard Ajax Push capabilities of open-source ICEfaces with these critical enterprise-grade features:
- Multi-application Support. EPS supports concurrent use of multiple ICEfaces push-enabled applications on the same application server (host-name) in the same client browser. The ICEfaces open-source ICEpush library can only support a single push application from the same server (host-name) in the same browser at one time.
- Distributed management of blocking push connections across a cluster for increased application scalability.
- Load-balancing of Ajax Push connections across a cluster for increased application scalability.
- Fail over of Ajax Push connections across a cluster for high application availability.
- Asynchronous Request Processing (ARP) integration for increased Ajax Push scalability.
Core Framework Extensions
ICEfaces EE includes the Core Framework Extensions library that can improve the ICEfaces experience on EE-certified platforms:
- Embedded HTML Compatibility for Facelets Applications - Configurable support for wrapping HTML markup in Facelets pages into components at runtime.
- View Root State Manager - Completely avoids unnecessary state saving and restoration of the server-side component tree resulting in significantly reduced server CPU utilization and memory consumption.
- [EPS Poller Application] - Demonstrates an Ajax Push application using EPS with various deployment scenarios, including fail-over support in a clustered deployment.
Functional & Load Testing Documentation, Tutorials, and Reference Materials
The ICEfaces EE Wiki includes extensive documentation, tutorials, and reference materials that clearly explain and demonstrate successful testing techniques for use with ICEfaces.
The ICEfaces EE Wiki provides extensive configuration and [deployment guides] for all supported application server and portal container platforms. In addition, server-specific [step-by-step instructions] are provided to enable fast, successful deployments for each of the following deployment scenarios:
- Stand-alone server
- Stand-alone server w/ EPS
- Clustered server w/ EPS (including fail-over)
An ICEfaces 3 to ICEfaces 4 Migration Guide is available for those wishing to migrate their existing ICEaces 3.x applications to ICEfaces 4.x.
- Oracle Mojarra JSF 2.2.1-2.2.14 (2.2.14 included).
- Oracle Mojarra JSF 2.3.5.
- Apache MyFaces JSF 2.2.x (2.2.12 included).
- Apache MyFaces JSF 2.3.1.
- Apple Safari 9 - 12
- Google Chrome 74
- Microsoft Edge
- Microsoft Internet Explorer (IE) 8 - 11 (MOBI Components require IE 10+)
- Mozilla Firefox 62, ESR 60
- Apple iOS 10.x+ (Safari)
- Google Android 6.x+ (Chrome)
Specific installation and configuration information for some platforms can be found in the [Server Configuration Appendices].
- Apache Tomcat 8.5, 9.1
- IBM WebSphere AS 8.5.5, 9.0
- Jetty 9
- Oracle Glassfish v5
- Oracle WebLogic Server 12c
- RedHat JBoss EAP 6.3, 7.0
- RedHat WildFly 14
When using Liferay, specific versions of the Liferay Faces Bridge must be used for each Liferay release version. See the Liferay Faces Version Scheme page for details.
Enterprise Push Server (EPS) Supported Platforms
| Apache Tomcat 8.5
|| Yes 1
| IBM WebSphere AS 8.5
| IBM WebSphere AS 9.0
| Jetty 9
| Oracle GlassFish 5
| Oracle WebLogic Server 12c
| RedHat JBoss EAP 7.0
| RedHat WildFly 14.x
1 Requires ActiveMQ 5 for JMS support
The following section describes the most commonly encountered known issues with this release:
- Client state saving mode is not supported by ICEfaces - it is required to use SERVER state saving mode.
- It is required to specify "h:head" and "h:body" tags in your ICEfaces application pages.
- The following standard "h:" components are not supported by the deltaSubmit feature (due to a problematic rendering technique that they utilize):
- The work-around is to use similar alternative components instead, such as ace:simpleSelectOneMenu, ace:list, or ice:selectOneMenu.
- ICEpush (icepush-ee.jar) asynchronous update support is limited to a single ICEfaces application per host-name/server.
- Viewing multiple ICEfaces applications in the same browser from the same host server concurrently will result in only one of the applications having functional push capabilities.
- Support for pushing asynchronous updates to multiple ICEfaces applications from the same server/host-name requires the use of the Enterprise Push Server (EPS).
- Session State Serialization
- By default, MyFaces serializes the state of the view into the session on every single request. While this allows the state of the view to be restored for that particular request, it can have an impact on performance as well as components that may not be designed for it. For these reasons we recommend to set the following context parameter in your application:
- See JIRA for a detailed explanation.
- The following features rely on HTML5 support in the browser, and are not supported on IE8 or IE9:
- All MOBI components
- ace:gmap (Google Maps doesn't support IE8 or IE9)
- ace:audioPlayer and ace:videoPlayer
- ace:textEntry "secret" mode is not supported on IE8.
- The transition animation effects are not supported on IE8 browsers to maintain performance and reliability.
- iOS Safari Browser
- Window Scope functionality is restricted when running on the iOS variant of the Safari browser. The iOS Safari browser does not fire the "beforeunload" event when a page is unloaded. This interferes with ICEfaces Window scope tracking that relies on the mentioned event as noted below:
- Using redirect navigation will result in a new Window scope instance being created for the target page of the redirect. The best workaround for this issue is to use forward navigation (where the redirect tag is not used in the navigation rule) instead. This will ensure that the window state is not lost (see ICE-11301).
- Window scope instances will not be proactively cleaned up when the window is closed, but will be cleaned up when the session expires (see ICE-10326).
- JBoss EAP 6.3, WebLogic 12c, WebSphere 8.5 (JEE 6 Platforms)
- It is required to have a supported Mojarra JSF 2.2 runtime installed and/or deployed with your application. This may require updating the JSF runtime libraries depending on which JSF version is currently installed in the server.
- Detailed instructions on how to deploy your application along with updated JSF libraries are provided in the ICEfaces EE Wiki [Server Configuration Appendices].
- Liferay 6
- Using the ACE Components with Liferay 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. See the Custom ACE Styles for Liferay Portal Wiki topic for details.
- ICEfaces Showcase Portlets
- The ICEfaces Showcase Portlets are intended to be used with a single instance of each demo portlet on the same page at one time. Adding the same demo portlet to the page multiple times will result in component failures.
- This issue is related to the id-usage and structure of the demo application itself, and is not an inherent limitation of ICEfaces or the components themselves.
- ICEfaces 4 does not require specialized IDE integration bundles, but rather can be used directly with leading JSF 2.2-supporting IDEs.
- IDE tutorials are available to explain the steps required to configure your NetBeans or Eclipse IDE projects for ICEfaces 4: IDE Tutorials for NetBeans and Eclipse
3rd Party Libraries
The license and version information for all required/included 3rd Party libraries for this release is available here.
Please report any issues with this release to ICEsoft Customer Support.