In our previous JDJ article - Rich Internet Components with JavaServer Faces
- we discussed how JavaServer Faces can fulfill new presentation requirements
without sacrificing application developer productivity building Rich Internet
Applications (RIA). We discussed how JSF component writers can utilize
technologies, such as AJAX and Mozilla XUL, to provide application developers
with rich, interactive and reusable components.
In order to use AJAX and Mozilla XUL with JSF, component writers have to make
sure to provide any resource files need by these technologies, such as
images, style sheets, or scripts. The standard approach to providing resource
files for a JSF component library is to serve them directly out of the web
application root file system. These resources are usually packaged in an
archive (such as a ZIP file), and shipped separately from the JSF componen... (more)
This article is based on, and contains excerpts from, the book Pro JSF:
Building Rich Internet Components by Jonas Jacobi and John Fallows, published
by Apress. Book is available on fine bookstores and Amazon.
In our previous article - "Rich Internet Components with JavaServer Faces"
(JDJ, Vol. 10, issue 11) - we discussed how JavaServer Faces can fulfill new
presentation requirements without sacrificing application developer
productivity building Rich Internet Applications (RIA). We discussed how JSF
component writers can utilize technologies, such as AJAX and Mozilla XUL, to
Apica, a performance testing and monitoring company teamed up with Kaazing to
bring performance monitoring to apps using WebSockets. Kaazing customers
moving applications to HTML5 and WebSocket extensions will now be able to
validate response time and function with Apica’s real-browser monitoring to
improve the end-user experience – Press Release.
Apica also published an excellent blog post about the Apica-Kaazing
partnership, and some insight into WebSocket monitoring. The snippet below
discusses the layers you need to think about when it comes to monitoring.
For a full read, hea... (more)
In Part 1, we looked at the completed application, which we’ll start
Before we get started with actual development, let’s take a look at the
starting application. Open a new browser tab or window with the starting
application in JSFiddle.
The starting app is as simple as it gets. First, take a look at the HTML
code, then read the explanations below the code snippet.
Kaazing WebSocket Tutorial - JMS