One of the key promises of Java Server Faces (JSF) was that it would provide a standard Java client-side component technology, allowing for JSF-compliant components to be mixed and matched in an application.
As JSF components become more sophisticated and interactive, however, developers must increasingly be careful about component interoperability, according to Steve Maryka, CTO of ICESoft, a JSF component vendor. The reason has not much to do with JSF itself, but with the various Ajax libraries sophisticated JSF component rely on in their implementation.
For example, many components use
|Steve Maryka, CTO of ICESoft, talks about the dangers of using multiple Ajax toolkits on the client. (6 minutes 15 seconds)|
What techniques have you found useful to avoid Ajax framework collision?Post your opinion in the discussion forum.
Bill Venners is president of Artima, Inc. He is author of the book, Inside the Java Virtual Machine, a programmer-oriented survey of the Java platform's architecture and internals. His popular columns in JavaWorld magazine covered Java internals, object-oriented design, and Jini. Bill has been active in the Jini Community since its inception. He led the Jini Community's ServiceUI project, whose ServiceUI API became the de facto standard way to associate user interfaces to Jini services. Bill also serves as an elected member of the Jini Community's initial Technical Oversight Committee (TOC), and in this role helped to define the governance process for the community.
Frank Sommers is Editor-in-Chief of Artima Developer. He also serves as chief editor of the IEEE Technical Committee on Scalable Computing's newsletter, and is an elected member of the Jini Community's Technical Advisory Committee. Prior to joining Artima, Frank wrote the Jiniology and Web services columns for JavaWorld.