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, 7Portal Containers.

• 10(1) Patta Copy Download
• 10:1 Ratio

Apache Pluto 2.0.3. Liferay Portal 5, 6Apache Pluto 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.Liferay Portal Portlet deployments may use either the Liferay Faces Bridge 3.1.RC2 (available from ), or the included PortletFaces Bridge library. Note that Mojarra 2.1.4 introduced a dependency on Servlet 3.0 APIs, as a result, it should not be used on older JEE5 application servers. Instead, Mojarra 2.1.3, or Apache MyFaces 2.1, should be used on JEE5 servers.

Note that the Mojarra JSF releases prior to 2.1.3 and greater than 2.1.6 have several serious issues that may impact your project and are not recommended. We are working with the Mojarra team to ensure future Mojarra releases (2.1.10) will resolve these issues. When running a JSF application in JSF2 PROJECTSTAGE='Development' mode, 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 PROJECTSTAGE='Production' in the web.xml file.MyFaces JSF. Myfaces 2.1.8-ICE-8229 is a specially patched MyFaces 2.1.8 library required for use with this release.

10(1) Patta Copy Download

See for details on the nature of the patch. 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.Browsers.

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. 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.

10:1 Ratio

It may be necessary to customize the themes to avoid conflicts when using the ACE components with Liferay 5. See the Wiki topic for details.Sample Applications. 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.SupportOpen source community support is available at.The are available for questions, comments, or general discussions regarding ICEfaces.Labels parameters.