Disabling ICEfaces

Version 1 by Deryk Sinotte
on Feb 08, 2012 14:55.


 
compared with
Version 2 by Deryk Sinotte
on Feb 08, 2012 15:00.


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

View page history


There are 1 changes. View first change.

  {warning}Page is currently viewable internally to ICEsoft group only.{warning}
  {warning}Page is currently restricted to internal viewing.{warning}
  
 ICEfaces makes it very easy to add Ajax capabilities to existing JSF applications. Simply adding the icefaces.jar to a JSF application will affect the necessary changes in the page markup to trigger the use of Ajax during interactions with components and during form submission.
  
 However, for certain diagnostic situations, it may be useful to turn off ICEfaces' automatic Ajax behaviour. For turning off ICEfaces for a selected view, you can can use the <icecore:config render="false"> tag on the relevant page. For additional details, see the description of the [<icecore:config>|config] tag.
  
 If you need to deactivate ICEfaces event capturing in a more specific and selective way, you can simply disable Ajax for that form:
  
 {code}
 <h:form >
  <f:ajax disabled="true" />
 {code}
  
 However, since the <f:ajax> tag is a standard JSF feature, disabling ICEfaces this way may have unintended side effects during JSF processing. In those cases, ICEfaces provides a custom form attribute:
  
 {code}
 <h:form >
  <f:attribute name="DISABLE_CAPTURE_SUBMIT" value="true" />
 {code}
  
 If the form element contains the attribute {{DISABLE_CAPTURE_SUBMIT}} then the automatic Ajax capturing function ice.captureSubmit() is not written, effectively disabling ICEfaces event capturing.
  
 {note}This attribute is intended for diagnostic purposes only. It may be changed or removed in future releases.{note}

© Copyright 2017 ICEsoft Technologies Canada Corp.