Professional Documents
Culture Documents
2007 NTG
Problem Statement
Web is ubiquitous Browser based applications are the future How to Develop Rich Client Application or Rich Internet Applications How to add Interactivity, animation, events and server data fetch functionality without reloading the pages How to manage content changes without refreshing the whole content
Ajax Architecture
User makes initial request against a given URL Server returns original HTML page Browser renders page as in-memory DOM tree User activity causes subsequent request against another URL asynchronously, leaving existing DOM tree untouched Browser returns data to a callback function inside the existing page Browser parses result and updates in-memory DOM with the new data, which is then reflected on screen to the user (the data page is redrawn, but not "refreshed")
Partial Refresh
Re-Rendering
"reRender" is a key attribute. The attribute allows to point to area(s) on a p g that should be updated as a response on ( ) page p p Ajax interaction. The value of the "reRender" attribute is an id of the JSF component or an id list.
10
11
12
13
14
15
Rich Components
<rich:panel />
<rich:dropDownMenu/>
16
Rich Components
<rich:tab/>
<rich:editor/>
17
Rich Components
18
19
20
<a4j:support/>
The <a4j:support> component is the most important core component in the RichFaces library. p y It enriches any existing non-Ajax JSF or RichFaces component with Ajax capability. All other RichFaces Ajax components are based on the same principles <a4j:support>
21
A4j:status
The <a4j:status> component generates elements for displaying of the current Ajax requests status. p y g j q There are two status modes: Ajax request is in process or finished.
22
Unit summary
Having completed this unit, you should be able to: Explain the use of JSF RichFaces Technology Technology.
23