This post originated from an RSS feed registered with Java Buzz by dion. Original Post: Apache Beehive PageFlows vs. Spring WebFlow Feed Title: techno.blog(Dion) Feed URL: http://feeds.feedburner.com/dion Feed Description: blogging about life the universe and everything tech Latest Java Buzz Posts Latest Java Buzz Posts by dion Latest Posts From techno.blog(Dion)

Way back in time I worked on early releases of BEA's Portal server. At the time they had their own MVC framework webflow, and it was a little painful to use (Remember the Rational ROSE tools for the Commerce product?).

However, that was many many years ago, and it has gotten better each release.

Now a lot of the same learning, is in place with Apache Beehive NetUI and PageFlows frameworks.

The Spring guys came out with a WebFlow component, which covers some of the same ground. How do they compare? At a high level their pro's are:

Spring WebFlow:

WebFlow, although immature, does have an interesting goal in that it works on top of ANY web framework, and isn’t restricted to NetUI/Struts. This will bring in many people, and is a common thread on the fact that makes people like Spring. They ‘feel’ that they are not locked in to things, and that Spring supports all (even if this is not reality).

Beehive PageFlows:

PageFlows has grown from many years of BEA products and has a lot of great, well thought out features. In fact, it was one of the easiest pieces for us to use on the port.

Some good stuff here, and I hope the best of both will come together.