Documentation Index. ICEfaces Logo. Release Notes. ICEfaces Release Notes. Getting Started Guide. ICEfaces Getting Started Guide (Pdf). ICEfaces Documentation. Added by Deryk Sinotte, last edited by Ken Fyten on Feb Building and Running ICEfaces with Ant · Key Concepts. Click here to see the current ICEfaces release documentation (3.x). The ICEfaces Component Suite includes enhanced implementations of the JSF standard.
|Published (Last):||6 July 2015|
|PDF File Size:||16.67 Mb|
|ePub File Size:||11.5 Mb|
|Price:||Free* [*Free Regsitration Required]|
While this is transparent to the developer, it does lead to certain restrictions.
This section describes how to use ICEfaces for portlet development. Printed by Atlassian Confluence 2. For reference, the complete taglib documentation for this component is available here.
If you want to use a different character, set it with the placeHolder attribute.
When, this component is not marked as requiredthen the text specified in the optionalIndicator is going to be rendered.
ICEfaces 4 API Documentation – ICEfaces – Community Wiki
Each individual component demo has been configured as a separate portlet that can be added and removed from a portal page. Define the collection of axes that will be used for the y-axis. This is an important distinction for the scope of managed beans and bean inter-dependencies. As with portlet modes, we recommend using the title bar icons to control these states rather than trying to adjust them programmatically.
ICEfaces 4.x Documentation
Must be a collection of ChartSeries type objects. Since ICEfaces directly handles all its own AJAX traffic directly, bypassing the portal container, it can be easy to make incorrect assumptions about the number of beans being created and the relationship between them.
Fortunately, Liferay provides configuration parameters that allow the developer to specify that a full render pass is required. In other words, ActionRequests are never really issued.
The ICEfaces portlet component is designed to behave unobtrusively in a regular web application. In this case, you can open two separate instances of the chat portlet on a single page and chat between them, watching them both update as messages are sent. Resourceas the basic example below. Once you have the PortletRequest, you can access the PortletPreferences which can be used to get and set preferences:.
Fired on a keypress event. This behavior can undermine the benefits of using ICEfaces in your portlet development.
MaskedEntry – ICEfaces – Community Wiki
If you want to store and retrieve attributes that are visible to multiple portlets, which can be useful when doing AJAX push, you should ensure that you use the application scope parameter:. Java Documentation This section covers attributes involved in the typical use-cases for this component. Confusion occurs if the developer assumes that the session and request beans for portlet A can reference or see the session and request beans for portlet B.
Table of Contents Loading HELPare still supported but have been deprecated.
ICEfaces JSF Components
The style of graph that the data is to appear documentaion, in the form of SeriesType. Otherwise a compatibility library is used which doesn’t support this functionality.
You can use the ExternalContext object to access the portlet session for storing and retrieving session attributes. We define static portlets as portlets that are built using more traditional technologies and without AJAX.
Powered by Atlassian Confluence 2. Currently, all interactive types of documentatioon are handled by the ICEfaces framework directly and are therefore never handled by the portal container. If you mix ICEfaces portlets on a portal page with these traditional portlets, you’ll get the behavior of the lowest common denominator.
The custom class names and styling specified in styleClass and style are applied on the a or input docimentation, depending on the value of the type attribute. You can see that the portlet component is wrapped around the actual content of what we want to see in the portlet. However, if the asynchronous ICEfaces portlets running on a single page are deployed in different.
Request-scoped beans are scoped documentaation the requests for the individual portlet. When this component is marked as invalid by the app, it will be rendered with the CSS class ui-state-error.