![]() The new approach for showing dialogs requires the full id of the dialog to be specified, such as "j_idt77:qrDialog" instead of just "qrDialog". The reason for this change is to enable lazy-initialization of the ACE component JavaScript objects to improve runtime performance and reduce browser memory use. The "widgetVar" attribute on the ACE components has been removed in ICEfaces 4 and in its place a new "()" client JavaScript object lookup API has been introduced. Referencing ACE Component Client Objects (widgetVar) Note that it may still be desirable to specify mandatoryResource for certain components in order to force their resources to be loaded at page-load time instead of dynamically when they are first rendered. The use of mandatoryResourceConfiguration for dynamically added components is no longer necessary, so long as "='true'" (default). mandatoryResourceConfiguration No Longer Required The ace:ajax and/or f:ajax tags can be used in place of the old icecore:singleSubmit tag. See the ace:ajax Wiki topic for more information. ![]() The ace:ajax tag provides a large set of configurability in terms of the scope of execution and rendering for ajax submits, as well as which client-events should trigger the submits, and a mechanism for intercepting the submit with a custom client-side JavaScript callback, checking the submit status, etc. It is possible and safe to wrap a form or set of components on the page with both an f:ajax and ace:ajax tag if you are using mixed "h:" and "ace:" or "mobi:" components. The ace:ajax tag must be used in conjunction with ACE and MOBI components, and the f:ajax tag must be used with any JSF standard "h:" components. The "icecore:singleSubmit" tag and related "singleSubmit" attributes on various ACE and MOBI components have been removed in ICEfaces 4 in favour of the more JSF-compliant "ace:ajax" tag mechanism for triggering ajax submits with partial page processing and or rendering. ![]() See the ICE to ACE Component Migration Guide topic for more information. Existing applications will need to replace the "ice:" component references with suitable ACE or MOBI alternatives. The legacy ICEfaces ICE (Compat) Components are not supported in ICEfaces 4. Referencing ACE Component Client Objects (widgetVar). ![]() The purpose of this guide is to provide information regarding changes made in ICEfaces 4 that may impact the behaviour of existing ICEfaces 3 applications, or may represent changes to previously established best-practices for ICEfaces application development. ![]()
0 Comments
Leave a Reply. |