6 5 push pages not updating
Using the methods outlined in Listing 1 through Listing 3, you establish a framework for a managed bean to monitor changes of the server-side data.
The workflow is, when the managed bean gets the notification that the server-side data has been changed, the is invoked and the data model is updated.
The dynamic GUI elements in this case are the category links (see Figure 1).
If the user clicks a specific category on the home page, he will be redirected to a new page that contains detailed information for all the books in this category.
At this time, JSF has no good solution to this problem.
If you check the standard life cycle of JSF, you will find that the user normally needs to produce an event on the Web page (by clicking a button, for example) to invoke the GUI refresh.
This means that even though dynamic elements can be created and added to a Web page during the run time, the Web page will not be refreshed automatically without interaction from the user.
For example, you would want a poll Web site to update the poll results as soon as its database receives new votes, or you might need a stock Web site that periodically updates real-time trading data of securities.
The poll results and the real-time trading data are dynamic elements that are unknown until run time, but elements that should be added or updated when the server side sends a signal. A previous developer Works article, "Craft Ajax applications using JSF with CSS and Java Script, Part 2: Dynamic JSF forms" explains how to hide and display optional JSF components without refreshing a Web page.If deleting the policy folders on the Microsoft Domain Controller (s) does not resolve the issue, clear the locally cached policies on each Xen App Server in the farm followed by running a gpupdate /force on each server.