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):||26 March 2007|
|PDF File Size:||1.22 Mb|
|ePub File Size:||11.19 Mb|
|Price:||Free* [*Free Regsitration Required]|
This behavior can undermine the benefits of using ICEfaces in your portlet development. For a comprehensive discussion of the contents of the portlet. Even though we have a single faces-config. From there you can retrieve information specific to the current portlet’s configuration:. You can see that the portlet component is wrapped around the actual content of what we want to see in the portlet.
However, these portlets also share a single set of configuration files web. Once you have the PortletRequest, you can access the PortletPreferences which can be used to get and set preferences:. In the above example, boldface text is used only to call attention to the relevant parameters in the code example.
ICEfaces provides the same benefits to portlets as it does to web applications. You can store information in the global user session so that it is available to all the portlets in a single user’s session by using the Portal API and specifying the application scope.
Listener method that will be notified when a new value has been set for this input component. 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. A confirmation dialog is displayed before sending the request.
Chart transforms Java data objects into a variety of graphical client representations. We also provide a build of Component Showcase that can be deployed in a portal container.
ICEfaces Documentation – ICEfaces – Community Wiki
Once this is done and an 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.
All input is optional. Portlet windows can also be in various states e.
Attributes in the PortletSession object can be stored in different scopes. If possible, you should consider porting the static portlets to use ICEfaces.
By default the mask function uses underscore to denote input points in text box. If you downloaded the docummentation code distribution of ICEfaces, then you can build all the samples by running:. The state map provides an API for looking up the state of a particular node object, as well as dcoumentation look-ups to get node objects with a particular state.
An array of data that you wish to use for the list components. The converse is also true, all changes in the state of the tree made programmatically in the server side are reflected in the client side as well. The old parameter, com. The data can be supplied to the tree as a List of a javax. When the user of the portlet interacts with those controls, the portal container can interpret the incoming request as an ActionRequest and process it accordingly. EDITand com.
All of this would look as follows. Custom request attributes can be specified icefwces space separated strings in com. JSF-based solutions can hook into the implementation in incompatible ways. TagLib Documentation This section covers attributes involved in the typical use-cases for this component. For reference, the complete taglib documentation for this component is available here.
Must be an element of chart. 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 default build of the portlet samples is Liferay running on Tomcat 6. For example, the following calls are equivalent:. If you have questions, please consult the portal vendor’s documentation for additional help. As noted, additional attributes iceafces be added to the context parameter as long as they are separated by spaces.
We recommend deploying it as a servlet in this case to minimize the additional configuration required. Please note that you cannot combine two graph types from different series types. TagLib Documentation This section covers attributes involved in the typical use-cases for this component.
The current specification for enterprise Java portlets is JSRwhich details the portlet-specific APIs that are supported by the portal container as well as the configuration artifacts that are required. These stylesheets were designed with web applications in mind.
ICEfaces JSF Components