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.

Author: Zulkimuro Virisar
Country: Bolivia
Language: English (Spanish)
Genre: Business
Published (Last): 11 March 2015
Pages: 445
PDF File Size: 15.84 Mb
ePub File Size: 7.85 Mb
ISBN: 549-2-57166-768-3
Downloads: 79333
Price: Free* [*Free Regsitration Required]
Uploader: Samugore

Powered by Atlassian Confluence 2. Must be an array of chart. Java Documentation This section covers attributes involved in the typical use-cases for this component.

ICEfaces 4 API Documentation – ICEfaces – Community Wiki

Application-scoped beans are visible across all the portlets in the archive as you would expect and this can be useful if all the portlets need to share some common state. But because ICEfaces does this without going through the portal container, the portal container does not know the mode has changed and since the portlet developer cannot access the ActionResponse API, there is no way to let it know.

Attributes in the PortletSession object can be stored in different scopes. For reference, the complete taglib documentation for this component is available here. Chart via an ajax page update, this results in a misrendered chart and documentatiom ‘Invalid Argument’ exception being raised. Chart transforms Java data objects into a variety of graphical client representations.

Must be an element of chart.

The reason for this change is to enable lazy-initialization of the ACE component JavaScript objects to improve runtime performance and reduce browser memory use. The MaskedEntry component allows a user to more easily enter fixed width input where you would documeentation them to enter the data in a certain format. The Component Showcase application is a useful way to see ICEfaces components in action as well as providing useful coding examples. TreeNode implementer or as an instance of a NodeDataModel.


If the portal vendor provides a client-side or server-side mechanism for handling these scenarios, then you have the option of using those.

A unique aspect of the ICEfaces documentarion is that, due to the use of AJAX techniques, requests can be “long-lived”- somewhere between request and session scope.

For attributes that are specific to the portal container, Dcumentation provides a mechanism for the developer to add them. The process of developing and deploying portlets to the various portal containers is vendor-specific so you should be familiar with the platform you are using. You can use the ExternalContext object to access the portlet session for storing and retrieving session attributes.

This behavior docuemntation undermine the benefits of using ICEfaces in your portlet development. For example, to access request attributes, you can do the following:.

For reference, the complete taglib documentation for this component is available here. In the following example, boldface text is used only to call attention to the relevant settings in the code example.

Must be called once for each desired datapoint. The reason docmuentation this change is to enable lazy-initialization of the ACE component JavaScript objects to improve runtime performance and reduce browser memory use. To maintain this data, ICEfaces makes use of the standard servlet and portlet APIs to get and store things like attributes in its own internal structures.


The last rule specifies the plus sign inside a circle. The position specified by labelPosition will determine where this label is going to be rendered; the possible values are left, right, top, bottom, none and inField to render the label in the field itself.

ICEfaces has its own portlet, which could be considered iceaces bridge of sorts, that handles incoming calls from the portal container and passes them on to the ICEfaces framework.

The problem prevents Firefox from working properly. Resource, allowing for greater control and flexibility. Note that reordering is not supported when using icefacs lazily-loaded tree data model.


Session-scoped beans are scoped to the portlet session rather than the user session which means that each portlet gets its own instance. This way documentayion series of different types can be plotted on the same Chart. To use the portlet component, add it as the top-level component of your content.

It is possible to combine docu,entation and asynchronous ICEfaces portlets on a single portal page without any kind of additional configuration, as long as the asynchronous ICEfaces portlets are deployed from the same.

ICEfaces Documentation Index

Table of Contents Loading For example, the style, portlet-form-button, is a style name that is used to determine the style of the text on a button. It should look something like this:. The standard way for a portlet to change the state of its underlying model is via an ActionRequest. In your code, you get access to the ExternalContext as follows:. 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.

If your portlets don’t need to share state for any meaningful reason, then it’s probably better to deploy them in separate archives. They are added to the portlet section as shown in this snippet:. Now let’s assume we have two portlets, A and B, declared in the. First, you’ll have to define a CSS rule specific enough to override the tree icon styling. Must be a collection of ChartSeries type objects.

This is an imperfect solution, so some mild rendering difference are bound to exist.