Q: How does ICEfaces enhance the application development lifecycle for developers or development teams that are using it?

A: ICEfaces is a pure Java Enterprise solution, so it enhances the development lifecycle, by not changing it. The Enterprise Java developer applies existing methodologies and best practices during development. All Ajax interactions are transparent to the developer, so he can work the way he is used to. Existing Java IDEs and test tools can be leveraged during development.

Q: What types of applications is ICEfaces used with?

A: Any Java-based web applications that requires a rich user interfaces can benefit from using ICEfaces. Applications that require “push-style” dynamic updating of the client presentation are particularly well matched to the ICEfaces Ajax Push capabilities. We have customers building applications in a large cross-section of industries with particular strengths in the financial sector where security is a major concern. ICEfaces utilizes a server-centric approach that fosters inherent security advantages over client-centric approaches.

Q: Can you walk me through a scenario of a customer using ICEfaces?

A: Typically, the customer will have legacy Java EE applications that they are looking to upgrade with a richer, more effective user interface. They are looking to preserve as much of their application infrastructure as possible. In some cases they have identified JSF as the standards-based approach they intend to follow, and are using ICEfaces to extend JSF with Ajax capabilities in a transparent way. In other cases, they are looking to add Ajax capabilities to their applications but are wary of, or have already suffered a negative experience with JavaScript and low-level, client-side Ajax programming. In the later case, migrating to JSF is a secondary consideration.

From a development environment perspective, they are looking to use their existing tools and development best practices. They typically use one of the ICEfaces IDE integration bundles to add ICEfaces to their existing tools, and continue to develop with their standard methodologies.

Most of the technical work is in redesign of the UI to provide the new Ajax-enabled interface, and binding the JSF/ICEfaces UI to the existing back-end data model.

Q: How does ICEfaces help the development manager? In other words, where’s the ROI?

A: The justification for introducing RIAs is they make the user more effective, so that represents the ‘R’. The development manager influences the ROI by minimizing the ‘I’. When introducing Ajax techniques to the development process, if you can reuse existing practices, tools, and most importantly, resources, you minimize the additional investment required to meet the demand for RIAs. Essentially, ICEfaces provides the path of least resistance for Java Enterprise Development Managers to bring RIA capabilities to the existing development team.

Q: What’s the advantage of using ICEfaces?

A: Use it and you get RIAs with minimal additional investment, don’t use ICEfaces and you don’t.

Q: What would you say are the three key features of ICEfaces?

A:

1) Standards-based, open source (JSF)

2) Transparent Ajax with pure Java programming model

3) Ajax Push

Q: How much does your ICEfaces cost?

A: Open source, so free. Support packages start at $2500.

Q: Where are you taking ICEfaces in the future?

A: More rich components is always on the list. New component rendering API’s will significantly reduce development effort for new rich components. Extensive portal integration work is underway. 2.0 architecture changes are on the horizon. Mobile Ajax support is being developed. Ultimately, the community drives the roadmap.