ICECORE Components

compared with
Current by Ken Fyten
on Nov 21, 2014 16:44.


 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 6 changes. View first change.

 h2. Core Tags
  {excerpt}
 h3.Overview
  
The ICEfaces 2 core framework supports the following tags in your Facelets markup:
  The ICECORE components provide a set of commonly required utility functions. These components typically have no visual rendering on the page but provide useful behaviors.
  
{anchor:icecoresinglesubmit}
  h3. ICECORE Wiki Topics
 {panel}
 {children:depth=2}
 {panel}
  
h3. <icecore:singleSubmit>
  h3. ICECORE API Documentation
 {panel}
 * [ICECORE Components TLD|http://res.icesoft.org/docs/v4_latest/core/comps/tld/]
 {panel}\\
  
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:
  
 {code:xml} <h:form id="form1" prependId="false">
  <icecore:singleSubmit rendered="true" />
  ...
 {code}
 More detailed information can be found in the [Single Submit] section.
  
 {anchor:icecoreconfig}
  
 h3. <icecore:config>
  
 You can use the ICEfaces configuration tag to adjust behaviour on a per page basis. To do so, add the <ice:config/> tag to the page and then set one or more of the following attributes:
  
 h5. ariaEnabled
  
 {code:xml}<icecore:config ariaEnabled="true"/>{code}
 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.
  
  
 {excerpt:hidden=true}
  
 h5. lazyPush
  
 {code:xml}<icecore:config lazyPush="false"/>{code}
 Allows control of lazy Ajax Push activation on a per-page basis. By default, when ICEpush is available, the Ajax Push feature will only activate when the first push request is called. By using this setting in in conjunction with the application-scoped org.icefaces.lazyPush context parameter, you can control the lazy activation of Ajax Push on a per-page basis.
 {excerpt}
  
 h5. render
  
 {code:xml}<icecore:config render="true"/>{code}
 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.

© Copyright 2021 ICEsoft Technologies Canada Corp.