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):||16 September 2013|
|PDF File Size:||8.79 Mb|
|ePub File Size:||9.16 Mb|
|Price:||Free* [*Free Regsitration Required]|
Doing this ensures that the ICEfaces bridge is properly initiated. Powered by Atlassian Confluence 2. Use “ant help” to see the list of available portlet container targets.
If you have questions, please consult the portal vendor’s documentation for additional help. TreeNode implementer or as an instance of a NodeDataModel. A set typically started empty to contain the list of values that have been selected. A type is an alternate representation of the same data that a series may render. Please check the documentation for your platform on how to deploy the portlet archive.
If you want icecaces use FontAwesome, then you’ll have to copy all the contents of the “fa” class from font-awesome. We recommend deploying it as a servlet in this case to minimize the additional configuration required.
While running portlets built with these other technologies may work, there is a definite possibility of conflict with ICEfaces. Doing this makes the ID hierarchy more efficient and helps the ICEfaces framework uniquely identify components on the page, which is important when more than one ICEfaces portlet is running.
You should use the new parameter, com. The implementation can modify the behaviour of the Resource in any way to better suit the purposes of the application. The impact of not being able to change portlet modes programmatically is that it becomes possible to have JSF navigation icefacees change the current view to a known mode without the portal container knowing about it.
The standard way for a portlet to change the state of its underlying model icefacss via an ActionRequest. If you don’t want these styles rendered out for your portlet, you can specify the following context parameter in the web. A future release of ICEfaces may deal with this situation but, for now, this is how it impacts the portlet developer.
You’ll have to look for the right FontAwesome character code that you want to use. For example, to access request attributes, you can do the following:.
In this case, you can open two separate instances documentatoon the chat portlet on a single page and chat between them, watching them both update as messages are sent.
ICEfaces JSF Components
Must be called once for each desired datapoint. The state map provides an API for looking up the state of a particular node object, as well as reverse look-ups to get node objects with a particular state.
Fortunately, Liferay provides configuration parameters that allow the developer to specify that a full render pass is required.
For reference, the complete taglib documentation for this component is available here. Even though we have a single faces-config. The old parameter, com. HELPare still supported but have been deprecated. Portlet windows can also be in various states e. Resource, allowing for greater control and flexibility. However, committing to these APIs probably means giving up the ability to run the portlet as a plain web application or running the portlet on a different portal platform.
This guide documents icefacss context parameter called, com.
API Documentation – ICEpdf – Community Wiki
There is a browser-specific issue when running ICEfaces portals on Jetspeed-2 which is related to parsing iceaces paths. The demo can be used to illustrate how to configure ICEfaces portlets as well as demonstrate working examples of the ICEfaces components running inside a portal.
Note that the remove button always makes a request to the server, whether an ajax event is used or not. Session-scoped beans are scoped to the portlet session rather than the user session which means that each portlet gets its own instance. If your portlets don’t need documentarion share state for any meaningful reason, then it’s probably better to deploy them in separate archives.
If, for some other reason, they are deployed in the icefacss archive, take care to manage the JSF configuration. For the developer, Liferay makes it easy to hot deploy and load portlets dynamically, which can be a big advantage in speeding up the development cycle. For example, the style, portlet-form-button, is a style name that is used to determine the style of the text on a button. An array of data documentatlon you wish to use for the list components.
ICE Components – ICEfaces – Community Wiki
The portlet developer generates interactive controls like buttons and links using the Portlet API. For a complete reference, please consult the JavaDoc.
Note that if you intend to produce a dynamic resourced based on some user input at the moment of clicking on this component, then you have to use the button type, in order to submit the form and process all input fields before generating and saving the resource, based on such input.
The client side component object is exposed through the global variable name specified in the widgetVar attribute.
You can see that the portlet component is wrapped around the actual content of what we want to see in the portlet. For single y-axis charts, define a single entry array. The problem prevents Firefox from working properly.