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):||27 August 2013|
|PDF File Size:||8.72 Mb|
|ePub File Size:||4.48 Mb|
|Price:||Free* [*Free Regsitration Required]|
Typically this is enabled when you want to use multiple windows of a single browser instance to concurrently view an ICEfaces application. The application-scoped bean is only created once and that single instance is referenced by both portlets. All the stat information will stay on the client until the containing form is submitted in another way. Samples that have been specifically developed as portlets can be found at:.
This component doesn’t use any default CSS class names. This component doesn’t have a client-side API made specifically to be used by application dlcumentation.
ICEfaces Component Suite Documentation
For a complete reference, please consult the JavaDoc. Table of Contents Loading The following is a sample code snippet of a portlet declaration with the specific ICEfaces information added:. This way multiple series of different types can be plotted on the same Chart.
The fileName attribute specifies the name used to save this file as, when downloading it as an attachment.
ICEfaces 4.x Documentation
If you want to store and retrieve attributes that are visible icdfaces multiple portlets, which can be useful when doing AJAX push, you should ensure that you use the application scope parameter:. If possible, you should consider porting the static portlets to use ICEfaces. The parameter name for the custom attribute has changed to more descriptive and consistent with other ICEfaces parameters.
Powered by Atlassian Confluence 2. Note that the remove button always makes a request to the server, whether an ajax event is used or not.
Powered by Atlassian Confluence 2. TagLib Documentation This section covers attributes involved in the typical use-cases for this component. 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.
The impact of not being able to change portlet modes programmatically is that it becomes possible to have JSF navigation rules change the current view to a known mode without the portal container knowing about it.
Issues that are specific to ICEfaces running on a specific portal implementation are covered in the following sections. User data and series-specific configuration is input via ChartSeries subclasses and passed as the ‘value’ property of the Chart component.
ICEfaces 2.x-3.x Documentation
A future release of ICEfaces may deal icefsces this situation but, for now, this is how it impacts the portlet developer. The client side component object is exposed through the global variable name specified in the widgetVar attribute. The Component Showcase application is a useful way to see ICEfaces components in action as well as providing useful coding examples.
For reference, the complete taglib documentation for this component is available here. Please note that you cannot combine two graph types from different series types. Printed by Atlassian Confluence 2. When setting the expansionMode and selectionMode attributes to clientevery time the user contracts, expands, or selects a node, a request to the server WON’T be made.
Table of Contents Loading The problem prevents Firefox from working properly. If you mix ICEfaces portlets on a portal page with these traditional portlets, you’ll get the behavior of the lowest common denominator.
Portlet windows can also be in various states e. You should use the new parameter, com. For example, to access request attributes, you can do the following:. Fired on a keypress event. While running portlets built with these other technologies may work, there is a definite possibility of conflict with ICEfaces.
Once this is done and documentattion instance is initialized, the component is added to the page, specifying this Resource instance, as well as other attributes that specify the way the resource is delivered. The last rule specifies the plus sign inside a circle. For an example of how to documdntation this, review the sample ICEfaces Chat portlet.
The type attribute specifies if a linkimageor button is displayed to the user to activate and download the resource. The label attribute specifies the label of the link or button when the resource is presented in these ways.
Powered by Atlassian Confluence 2. The attachment flag indicates whether the resource should be downloaded as an attachment, in order to force the browser to save the resource instead of trying to open it. For the developer, Liferay makes it easy to documentatkon deploy and load portlets dynamically, which can be a big advantage in speeding up the development cycle.
Must be called once for each desired datapoint. Resourceas the basic example below. This is an important distinction for the scope of managed beans and bean inter-dependencies.
Define the variable on the backing bean that will be displayed using this chart. To maximize the successful development and deployment of ICEfaces portlets, consider these tips and suggestions:. For reference, the complete taglib documentation for this component is available here. An array of data that you wish to use for the list components. The parameter names for the supported portlet modes have changed to be more descriptive and consistent with other ICEfaces parameters. As with portlet modes, we recommend using the title bar icons to control these states rather than trying to adjust them programmatically.
Use “ant help” to documebtation the list of available portlet container targets. 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.