This document will guide you through the process of porting Woodstock
applications to ICEfaces. The porting process is devised to be
evolutionary in nature, allowing you to maintain a functional Woodstock
application, while incrementally porting Woodstock pages to
ICEfaces. The ultimate goal of the porting process is to entirely
eliminate Woodstock from the application, leaving you with a pure
ICEfaces application where you can take full advantage of all the rich
features provided in the ICEfaces framework.
The migration support in ICEfaces is based on project-level coexistence with Woodstock, which means ICEfaces and Woodstock pages can coexist in the same web application. The approach is NOT intended to support page-level coexistence of ICEfaces and Woodstock, where components from both frameworks are included in the same page. That being said, subsequent releases of ICEfaces will include selectively ported Woodstock components that will exist as first-class citizens of the ICEfaces framework. The availability of these components will ease the page-level porting effort, but not eliminate it.
The majority of Woodstock applications are based on the Visual JSF project type in NetBeans, so this guide focuses on this particular migration path. If your application leverages Woodstock in some other programming model like Facelets, most of the concepts presented here will still apply. The guide is presented in three parts.