Core Tags

You are viewing an old version (v. 20) of this page.
The latest version is v. 31, last edited on Nov 21, 2014 (view differences | )
<< View previous version | view page history | view next version >>

Core Tags

To use any of the core tags, first declare the core namespace:

<html ... xmlns:icecore="http://www.icefaces.org/icefaces/core">

The ICEfaces 2 core framework supports the following tags in your Facelets markup:

<icecore:singleSubmit>

The <icecore:singleSubmit> tag is designed to allow submission from just the component generating the event and then update the page with any changes from all components. It's used in the following way:

<h:form id="form1" prependId="false">
    <icecore:singleSubmit rendered="true" />
    ...

More detailed information can be found in the Single Submit section.

<icecore:config>

You can use the ICEfaces configuration tag to adjust behaviour on a per-page basis. These settings take precedence over corresponding application global settings specified via context-param entries in the web.xml. To do so, add the <ice:config/> tag to the page and then set one or more of the following attributes:

ariaEnabled
<icecore:config ariaEnabled="true"/>

Allows control of DOM rendering on a per-page basis. By default, when ICEfaces is available, ARIA support is enabled. By using this setting in in conjunction with the application-scoped org.icefaces.aria.enabled context parameter, you can control whether or not ARIA support is active on an individual page.

mandatoryResource

[As of ICEfaces 3.0]

<icecore:config mandatoryResource="all|none|(space delimited list of components)"/>

A space-delimited list of components that will have their requisite resources pre-loaded on this page. The pre-loading allows the components to function correctly even if they are later added to the page dynamically. The values "none" (which is the default) and "all" are also valid. The value of this attribute on a page takes precedence over the values specified by the context parameter org.icefaces.mandatoryResourceConfiguration. See Configuration#mandatoryResourceConfiguration for additional details.

messagePersistence

[As of ICEfaces 3.0]

<icecore:config messagePersistence="true"/>

Allows control of message persistence on a per-page basis. By default, when ICEfaces is available, FacesMessages are persisted across different partial submits from the same page. This setting can be used to disable this behavior on a per-page basis.

render
<icecore:config render="true"/>

Allows control of DOM rendering on a per-page basis. By default, when ICEfaces is available, DOM rendering and partial page updates are enabled for stock JSF components. By using this setting in in conjunction with the application-scoped org.icefaces.render.auto context parameter, you can control whether or not ICEfaces is active on an individual page. See Configuration for additional details.

<icecore:push>

[As of ICEfaces 3.0]

You can use the ICEfaces push tag to configure push behavior on a per-view basis. To do so, add the <ice:push/> tag to the page and then set one or more attributes. A view can be added to one or more push groups by adding one or more occurrences of this tag.

group
<icecore:push group="groupName"/>

Allows control of the current view being added to a push group. This is a mandatory attribute specifying the group the view must be added to.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

© Copyright 2017 ICEsoft Technologies Canada Corp.