ICEfaces 3.0.0.RC2 Release Notes
December 22nd, 2011
These Release Notes include the following sections:
About This Release
ICEfaces 3.0 RC2 is a release-candidate preview build of ICEfaces 3. While substantial testing and verification has occurred against this release, it is not recommended for production use.
ICEfaces is available for download in the following formats:
Notable Changes in this Release
This release primarily includes bug fixes as we approach 3.0 final release.
- Optimized Resource Loading
- The following component attributes have been renamed to align with ACE component attribute naming conventions:
- 'onstart' is now 'onStart'
- 'onsuccess' is now 'onSuccess'
- 'onerror' is now 'onError'
- 'oncomplete' is now 'onComplete'
- NOTE: Applications using these component attributes will need to be updated to use the new names.
- Now supports the standard ThemeRoller CSS styling for the download button.
- ace:menuItem & ace:menuBar
- The ace:menuItem tag name has been changed from "ace:menuitem" to "ace:menuItem" (camel-cased) to align with the ACE component-naming standard.
- The ace:menuBar tag name has been changed from "ace:menubar" to "ace:menuBar" (camel-cased) to align with the ACE component-naming standard.
- The associated Java classes for the ace:menuItem and ace:MenuBar has also had their names updated to reflect capitalization of the "Item" and "Bar" suffices.
- NOTE: Applications using these component tags or classes will need to be updated to use the new names.
- An issue that resulted in the ace:tabSet flickering or rapidly resizing when switching between tabs when used in server mode has been resolved.
- Now supports the ability to auto-size itself based on the size of it's contents.
- Support for forms other than h:form
- ICEfaces should now work correctly with any well-behaved form tag, such as the LifeRay "aui:form".
- Previously only "h:form" was supported.
- Apache MyFaces
- The MyFaces JSF library included with this release has been updated to "JSF 2.1.3-ice-7517", which is a patched version of MyFaces 2.1.3. The patch increases the maxiumum URL length from the MyFaces standard 256 characters to 1024 characters. This was necessary to prevent resource loading issues when using MyFaces in portal containers. It is anticipated that the patch will be accepted into a future MyFaces official release.
- This release introduces support for using the Apache MyFaces 2.1.3 JSF runtime with the ICEfaces Advanced Components as well as within portal containers.
- Oracle Mojarra JSF
- The Mojarra JSF version included in this release has been updated to JSF 2.1.4.
- Note that Mojarra 2.1.4 introduces a hard depedency on Servlet 3.0 APIs, as a result, it cannot be used on older JEE5 application servers. MyFaces 2.1.3 should be used in on older JEE5 servers instead.
Samples & Tutorials
- ICEfaces Showcase Sample Application
- The showcase application has been updated to reflect component changes in this release.
- The showcase application should be considered in "preview" form.
- NetBeans 7.0
- This release provides an updated IDE integration for NetBeans 7.0.1.
- Note: Now requires projects to select the JSF library to use with ICEfaces (Mojarra or MyFaces).
- NOTE: You must update your NetBeans 7 installation with the latest module versions prior to installing the ICEfaces NetBeans integration. See the NetBeans Integration Release Notes for details.
- Eclipse 3.7
- This release provides an updated IDE integration for Eclipse 3.7.
- Features improved design-time renderers for the Advanced Components (ace).
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 3 - 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.
- URL Length Limit
- MyFaces 2.1.3 enforces a maximum URL length limit of 256 characters. This limit causes problems with some ACE resource URLs when used inside a portlet environment.
- To work-around this issue, ICEfaces 3.0.0.RC1 includes patched MyFaces 2.1.3 libraries that extend the length limit to 1024 characters.
- It is anticipated that this issue will be resolved in a future MyFaces official release.
- Auction Monitor (w/ MyFaces)
- AuctionMonitor's chat facility is not currently functional with MyFaces due to an issue that results in generated IDs being different in MyFaces than those created by Mojarra.
- This release includes the Mojarra JSF 2.1.4 runtime libraries.
- Mojarra 2.1.4 introduces a hard depedency on Servlet 3.0 APIs, as a result, it cannot be used on older JEE5 application servers. MyFaces 2.1.3 should be used in on older JEE5 servers instead.
- 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.4 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 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:
<Context antiJarLocking="true" antiResourceLocking="true"/>
- Glassfish 3 / JBoss 6, 7 (JEE 6 Platforms)
- It is necessary to have Mojarra JSF 2.1.0-FCS or greater (2.1.4 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.
- The showcase sample application is in "preview" form in this release. Minor issues exist in many of the demos at this time.
Open source community support is available at http://www.icefaces.org.
Please report any issues, questions, or comments regarding this release to the ICEfaces Development Build Feedback forum.
The ICEfaces community forums are available for questions, comments, or general discussions regarding ICEfaces.