In this way, you can turn a standard JSF application into an Ajax application simply by adding icefaces.jar. Note that ICEfaces does heavily emphasize Ajaxifying regular ol' JSF components - the ICEfaces RenderKit provides "Direct-to-DOM" implementations of the standard JSF components. The various RenderManagers allow you to schedule Ajax Push in a scalable fashion (using a bounded number of threads to handle arbitrarily many clients). ICEfaces provides RenderManagers that can be set up through dependency injection. There is optional configuration in faces-config.xml that you will likely want to make use of, however. We can provide an article on that explains the extension points. jar files contain the appropriate faces-config.xml settings that install the ICEfaces factory and ViewHandler. In terms of modifying faces-config.xml for ICEfaces, really nothing is required by the developer. jar files, we could do that in short order)? What maven features are required for Equinox and AppFuse Maven metadata for ICEfaces does exist (it was created for an important customer application) but at the time made sense only for their internal repository. Stephen O'Grady has an excellent writeup on this: And Sun Said, Set My Java Free: The Open Source Q&A. They require you to copy a bunch of static files (images, stylesheets and scripts) into your project. I was able to get it working in AppFuse fairly easily, but it's kinda ugly from a setup standpoint. OpenLogic decided to use Infragistics in the project I started for them. Update: I forgot to mention Infragistics NetAdvantage as a JSF Ajax framework. So I think Ajax4jsf still remains, and ICEfaces looks like a better out-of-the-box component library than Trinidad. The hard part is choosing which is a better Ajax toolkit: ADF Faces/Trinidad, Ajax4jsf or ICEfaces? Trinidad and ICEfaces seem to be more about components, whereas Ajax4jsf is more about Ajaxifying regular ol' JSF components. Unfortunately, integrating ICEfaces into your project is only the beginning. If someone wants to create the Maven bundles for ICEfaces, I'll try to carve out some time later this week to write up instructions for integrating ICEfaces into Equinox and AppFuse. I was somewhat motivated to write such a guide this morning, but lost motivation quickly as I realized it might be quite the effort. They do show how to modify your web.xml, but there doesn't seem to be a short, concise guide to what configuration settings you need to add to your faces-config.xml. Looking through ICEfaces documentation and sample apps, they seem to be missing a straight-forward "here's how to integrate it into your existing application" guide. Must be a tough market out there.Īpparently, ICEfaces works with Facelets, so it should work with AppFuse and Equinox. I do think it's interesting that the major JSF component vendors (Oracle, Exadel and now ICEsoft) have all open-sourced their products. Was this inspired by Java going GPL? 1 I doubt it, these things take time and it's likely that ICEsoft had this one in the cooker for quite a while. Today, ICEsoft announced they've open-sourced ICEfaces. I think it interesting that both products don't seem to care about capitalization, but I digress. I don't know that either one is a true open source project (where developers are from multiple companies), but Spring isn't either, so I don't know that it actually matters. As far as JSF Ajax frameworks are concerned, there seems to be two major players: Ajax4jsf and ICEfaces.
0 Comments
Leave a Reply. |