NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
You have to
see what ICEsoft has done to appreciate it.
Before you dive into all the technical details about ICEfaces, do yourself a favor and
just check out their demos.
I have watched these guys construct an application with ICEfaces, and I can say without a doubt that they make some of the hardest stuff easy. Their "Direct-to-DOM" approach frees you from having to poll your server for state changes in the server-side components, and they do a great job of showing how this can make you whole web application feel richer and more responsive.
JavaServer Faces has gotten a reputation for having a steep learning curve, but ICEfaces may be the much-needed equalizer for the perceived complexity of JSF. Since it is a JSF RenderKit at its core, you can enjoy lots of benefits by using ICEfaces in existing JSF solutions with very little additional code.
This is one helluva free product - well worth your time to check it out.
Demo link
and
download link
ICEsoft has an excellent product, but it's not the only way to do AJAX with JSF. As a matter of fact, most
commercial JSF component libraries
support AJAX transparently as well (and have for a while). And there are a few approaches, such as Exadel's
ajax4jsf
and Jacob Hookom's Avatar (presented at JavaOne), that provide transparent AJAX support for any JSF component. Even
BackBase
, which is known for its powerful AJAX GUI framework, has full JSF integration now.
The key thing here is that you get transparent AJAX support -- just develop a standard JSF application and you can take advantage of the "RIA" craze without writing any extra JavaScript or DHTML.
What sets ICEfaces apart from other JSF solutions is their ability to push changes out from the server, providing real-time interaction capabilities. And what's great is that you still get all of these capabilities with standard JSF development.
There's been a recent report on the forums of someone having some issues with certain ICEfaces components when using the "Tabbrowser Extension" in Firefox. Are you by chance using this extension?
It seems to have something to do with how long I wait until I click on an item in the tree on the left. If I click too early, it tends to hang. The CPU load stays at 50%, eventually the window goes white and I have to kill the process. If I wait until the page has finished loading, it works. Presumably that's because some large JavaScript libraries are downloaded and events have to be hooked up. I just wonder why it crashes the browser instead of doing nothing until everything is loaded.
Nice work there. Modal dialog shown is not quite a modal one. It is still possible to work with background window when modal dialog is open. I just clicked on "Back" context menu and modal dialog disappeared without having to close it.
Ajax is a modern development, but the face (no pun intended) of front-end components are always changing which makes the JSF technology feel stale before you even consider placing it.
Add to it the quasi-framework aspect and it's a "eh" feeling. Plus XForms seems like the eventual winner in this space, (Chibas anyone?), and there are completely cross-browser, cross-web-platform pure HTML/JS components like Dojo Toolkit available not to mention entire front-end platforms like Bindows.
I assume you know what I mean, but since you want to split hairs, the ability to perform "ajax" has been around for a while, but the average application leveraging that technology is a recent development. People are making it a core feature of their webapps now, instead of being a capability that was only a note-worthy feature of the Microsoft Exchange web interface.
JSF+Ajax > Ajax alone?
URL: ICEfaces Community Edition
At 11:45 AM on May 31, 2006, Rick Ross wrote:
Fresh Jobs for Developers Post a job opportunity
JavaServer Faces has gotten a reputation for having a steep learning curve, but ICEfaces may be the much-needed equalizer for the perceived complexity of JSF. Since it is a JSF RenderKit at its core, you can enjoy lots of benefits by using ICEfaces in existing JSF solutions with very little additional code.
This is one helluva free product - well worth your time to check it out. Demo link and download link
12 replies so far (
Post your own)
Re: JSF+Ajax > Ajax alone?
ICEsoft has an excellent product, but it's not the only way to do AJAX with JSF. As a matter of fact, most commercial JSF component libraries support AJAX transparently as well (and have for a while). And there are a few approaches, such as Exadel's ajax4jsf and Jacob Hookom's Avatar (presented at JavaOne), that provide transparent AJAX support for any JSF component. Even BackBase , which is known for its powerful AJAX GUI framework, has full JSF integration now.The key thing here is that you get transparent AJAX support -- just develop a standard JSF application and you can take advantage of the "RIA" craze without writing any extra JavaScript or DHTML.
What sets ICEfaces apart from other JSF solutions is their ability to push changes out from the server, providing real-time interaction capabilities. And what's great is that you still get all of these capabilities with standard JSF development.
Principal Consultant, Virtua, Inc.
Author, JavaServer Faces in Action
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
Re: JSF+Ajax > Ajax alone?
Unfortunately their demos make my browser (Firefox 1.5_03 on Windows) hang on three out of four attempts.Strange... I use exactly the same, Faui
I am also running Firefox 1.5_03 on Windows, but I have not had any difficulties with the demos. I wonder what is different?Rick
bestuff.com - the best stuff in the world
Re: JSF+Ajax > Ajax alone?
Faui,There's been a recent report on the forums of someone having some issues with certain ICEfaces components when using the "Tabbrowser Extension" in Firefox. Are you by chance using this extension?
Regards,
Ken
Re: JSF+Ajax > Ajax alone?
No, I'm running just the Adblock and Dom Inspector extensions.Re: Strange... I use exactly the same, Faui
It seems to have something to do with how long I wait until I click on an item in the tree on the left. If I click too early, it tends to hang. The CPU load stays at 50%, eventually the window goes white and I have to kill the process. If I wait until the page has finished loading, it works. Presumably that's because some large JavaScript libraries are downloaded and events have to be hooked up. I just wonder why it crashes the browser instead of doing nothing until everything is loaded.Re: JSF+Ajax > Ajax alone?
Nice work there. Modal dialog shown is not quite a modal one. It is still possible to work with background window when modal dialog is open. I just clicked on "Back" context menu and modal dialog disappeared without having to close it.Still not sold on the JSF.
Ajax is a modern development, but the face (no pun intended) of front-end components are always changing which makes the JSF technology feel stale before you even consider placing it.Add to it the quasi-framework aspect and it's a "eh" feeling. Plus XForms seems like the eventual winner in this space, (Chibas anyone?), and there are completely cross-browser, cross-web-platform pure HTML/JS components like Dojo Toolkit available not to mention entire front-end platforms like Bindows.
I dunno, just thinking out loud.
Re: Strange... I use exactly the same, Faui
+1 (no problem)Ajax modern ?
> Ajax is a modern developmentPlease explain, this is very old stuff.
It is painful to see the direction it is going.
Re: Ajax modern ?
I assume you know what I mean, but since you want to split hairs, the ability to perform "ajax" has been around for a while, but the average application leveraging that technology is a recent development. People are making it a core feature of their webapps now, instead of being a capability that was only a note-worthy feature of the Microsoft Exchange web interface.Re: Strange... I use exactly the same, Faui
I think you've identified the problem. The CPU loading increases but then returns to normal. You need to wait until that point or Firefox will crash.Still, interesting technology if you can be sure that end-users won't use Firefox.