ICEFaces入门学习

IceFaces training content 1. Why IceFaces? 1.1 What's IceFaces - An Internet technology that will allow you to easily build rich highly interactive web applications - An AJAX Framework - A server-side AJAX Framework - A JSF extension 1.2 Why IceFaces - more ‘ajaxy’ web application - stick to your server-side Java Enterprise skills - maintain productivity - build a collaborative web application with AJAX Push 1.3 Why not Javascript? - Cross-browser compatibility issues - Hard to find highly skilled JS developers - Challenging to maintain a large Javascript codebase 1.4 Major Benefits of ICEfaces - An Enterprise AJAX Solution - AJAX for server-side developers! - A Standards-based AJAX Solution – Server-side standards: JSF – Client-side standards: Javascript & CSS - Application or Page-level AJAX – AJAX functionality is built into the framework, not the components - Large Component Library - Compatiblity - Java App Servers - Web Browsers - Strong integration with other Java frameworks – Spring – JBoss Seam – Portlets – Myfaces Tomahawk - Strong “tooling” integration with popular Java IDEs: - Eclipse - MyEclipse - NetBeans - Automatic AJAX - Automatic inter-component communication and collaboration - Transparent AJAX - Direct-to-DOM (D2D) Rendering - d2d.PNG - AJAX Push 2. IceFaces basic instruction - ICEfaces is based on JSF - The JSF specification defines a number of extension points: – ICEfaces implements its rich UI and AJAX functionality as a set of JSF extensions – ICEfaces is primarily a JSF render kit extension – ICEfaces is also a component library - Architecture.PNG - How the page is constructed on the server - When the page is first requested, all of the presentation is sent to the client, including a JavaScript bridge.The avaScript bridge is the communication mechanism between the server and the client – When the user interacts with the client, events are sent back to the server that may alter application state and change the page on the server – When the page changes on the server, we deliver only those incremental changes back to the client - In a nutshell, this is what we call the Direct-to-DOM (D2D) approach. All client-server communication consists of presentation state updates, and events. This is a very-thin client approach. – No application logic on the client. No business logic on the client – Very small JavaScript footprint on the client - No need to care about the client-server communication channel - Write your applications as if they were traditional desktop applications - Partial Submit - Introduces a fine-grained user interaction model for intelligent form processing - Submit is partial in the sense that only partial validation of the form will occur. - The standard JSF validator mechanism can be leveraged, or any other arbitrarily complex or simple evaluation logic can be applied. - Partial.PNG - Useful IceFaces tag - Layout Components ice:panelGroup <div></div> ice:panelGrid <table/> ice:panelSeries ice:panelTabSet ice:panelCollabsible panelPopup - Input Components basic Auto-Complete Rich Text Editor <ice:inputRichText ice:inputTextarea File Upload ice:inputFile - Output Components - Selection Components 3. IceFaces in Alineo - The pages which used IceFaces - *.jspx - homepageTasks.jspx - Some useful experience - standard JSF to ICEfaces - convert all existing JSPs to IceFaces 4. More material about IceFaces - ftp://202.134.82.20/ice_faces/ - ICEfaces-1.8.1-bin.zip - ICEfaces-1.8.1-src.zip - ICEfaces Self-Serve Training.rar - http://www.icefaces.org/main/demos/ 5. Question