I have been pretty skeptical for a long time about RAD tools – the actual productivity gains in the short term and maintainability and componentization of code (or lack thereof) from a longer term perspective. However, I finally played with WebSphere Portlet Factory recently in a scenario where I was trying to hook up to a SAP system for basic information search and display. It was certainly a breeze with WPF to get a quick and dirty application built to achieve this goal. After this experience, I now believe that I am ready to invest some more time to evaluate WPF’s value. I will probably rely on a colleague to assist with the evaluation and piggyback off his efforts.
I can certainly see WPF being a great tool to put together some quick applications/portlets with a couple of screens but I am skeptical about doing complex multi-screen portlet development with WPF. Another potential value for some teams is that WPF also enables less-than-expert Java developers get simple portlets built and tested – provides a simpler on-ramp for developers new to Portals and/or Java development.
Joey@IBM had a blog entry on WPF and another one that is worth a read!
I hope to be back soon with more on WPF and its appropriate usage. Areas of investigation include automation of a build process for WPF portlets, WPF project artifact check-in, and possibilities for hand-editing of generated code.