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):||12 November 2018|
|PDF File Size:||8.52 Mb|
|ePub File Size:||11.44 Mb|
|Price:||Free* [*Free Regsitration Required]|
They are added to the portlet section as shown in this snippet:. Enables use of a NodeStateCreationCallback, which lazily initializes the component NodeStates based on a given node data object. If you downloaded the source code distribution of ICEfaces, then you can build all the samples by running:. The required parameters, render-weight and ajaxableare specified in the liferay-portlet. However, each portlet will, in essence get a copy of that configuration.
This would look like documentxtion. For a complete reference, please consult the JavaDoc. The old parameter, com. This behavior can undermine the benefits of using ICEfaces in your portlet development. Powered by Atlassian Confluence 2. Then this component is marked as requiredthe main input field receives the CSS class ui-state-requiredotherwise, it receives the CSS class ui-state-optional.
The resource attribute references the instance of the Resource object to serve. If, for some other reason, they are deployed in the same archive, take care to manage the Doucmentation configuration. Portlet users can drag and drop portlets on the page without requiring a full page refresh. If the portal vendor provides a client-side or server-side mechanism for handling these scenarios, then you have the option of using those.
ICEfaces Documentation, Release Notes and Guides – ICEsoft Technologies
EDITand com. All of this would look as follows. The portlet developer generates interactive controls like buttons and links using the Portlet API.
The last rule specifies the plus sign inside a circle. Check the ExternalContext JavaDoc to see what is provided by the rest of the API as some methods state specifically what they do differently in a portlet environment as compared to a servlet environment.
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.
With portlets, the main configuration document is the portlet. For an example of how to do this, review the sample ICEfaces Chat portlet. Anything else defaults to ‘null’ and does not allow any selections whatsoever. Powered by Atlassian Confluence 2.
The JSR specification also documents a base set of common styles that should be applied to specific page elements. A unique aspect of the ICEfaces framework is that, due to the use of AJAX techniques, requests can be “long-lived”- somewhere between request and session scope.
In addition, vendors implementing JSR typically have their own custom configuration options. The data can be supplied to the tree as a Iicefaces of a javax.
It is important to use the. Using the Portlet API. 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.
Attributes in the PortletSession object can be stored in different scopes. A separate request bean instance for each portlet is created for each request. For reference, the complete taglib documentation for this component is available here. The position specified by labelPosition will determine where this label is going to xocumentation rendered; documentatjon possible values are left, right, top, bottom, none and inField to render the label in the field itself. These CSS classes can be used to add custom styling to this component, in order indicate its current state in a more visual way.
This can be a powerful feature that can also be leveraged to do a form of inter-portlet communication IPC in certain configurations. The impact of not being able to change portlet icefacs 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.
For developing ICEfaces applications, you only need to be concerned with a couple of important settings: This section describes how to use ICEfaces for portlet development. Add a point of data to the graph icefacess be created. documenttation
If your portlets don’t need to share state for any meaningful reason, then it’s probably better to deploy them in separate archives. 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.