Comments on: Apache Beehive PageFlows vs. Spring WebFlow http://almaer.com/blog/apache-beehive-pageflows-vs-spring-webflow blogging about life, the universe, and everything tech Fri, 04 May 2012 14:57:05 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Dj http://almaer.com/blog/apache-beehive-pageflows-vs-spring-webflow/comment-page-1#comment-22142 Dj Sun, 15 Apr 2007 21:57:57 +0000 http://almaer.com/blog2/apache-beehive-pageflows-vs-spring-webflow#comment-22142 Quiero un gordo para mi plis Quiero un gordo para mi plis

]]> By: kiko http://almaer.com/blog/apache-beehive-pageflows-vs-spring-webflow/comment-page-1#comment-22141 kiko Mon, 09 Apr 2007 19:02:11 +0000 http://almaer.com/blog2/apache-beehive-pageflows-vs-spring-webflow#comment-22141 loco loco

]]> By: Rich Feit http://almaer.com/blog/apache-beehive-pageflows-vs-spring-webflow/comment-page-1#comment-22140 Rich Feit Sat, 09 Apr 2005 20:04:48 +0000 http://almaer.com/blog2/apache-beehive-pageflows-vs-spring-webflow#comment-22140 Speaking from the Beehive perspective (but not for BEA :))... being built on Struts has been *mostly* a great blessing. When we began work on Page Flow (mid-2001, long before Beehive became open source), Struts was just coming to prominence, and it made sense to leverage it (we started out with our own top-to-bottom MVC framework, but came to our senses and removed the whole tier that overlapped with Struts). This worked out smashingly -- over the years, we got to take advantage of all the work that was being put into Struts, while staying focused on adding an annotation-based and flow-centered (and highly-toolable) approach. That was before the explosion of web frameworks. Lately, being built on top of another piece of software seems to affront the whole 'light' ethic. Rather than building on each other or fading away, frameworks are integrating with each other and becoming more focused, and people are getting the chance to combine them for their different strengths. IMO this is a good thing. In this particular space there's a trend towards higher-level page flow abstractions -- thinking of entire flows as reusable units, and centralizing the controller logic/metadata/state (e.g., some of what Shale is starting to do in the JSF world). It'll be very interesting to see how the pieces fit together and where we all end up. Speaking from the Beehive perspective (but not for BEA :))… being built on Struts has been *mostly* a great blessing.

When we began work on Page Flow (mid-2001, long before Beehive became open source), Struts was just coming to prominence, and it made sense to leverage it (we started out with our own top-to-bottom MVC framework, but came to our senses and removed the whole tier that overlapped with Struts). This worked out smashingly — over the years, we got to take advantage of all the work that was being put into Struts, while staying focused on adding an annotation-based and flow-centered (and highly-toolable) approach.

That was before the explosion of web frameworks. Lately, being built on top of another piece of software seems to affront the whole ‘light’ ethic. Rather than building on each other or fading away, frameworks are integrating with each other and becoming more focused, and people are getting the chance to combine them for their different strengths. IMO this is a good thing. In this particular space there’s a trend towards higher-level page flow abstractions — thinking of entire flows as reusable units, and centralizing the controller logic/metadata/state (e.g., some of what Shale is starting to do in the JSF world). It’ll be very interesting to see how the pieces fit together and where we all end up.

]]> By: Keith http://almaer.com/blog/apache-beehive-pageflows-vs-spring-webflow/comment-page-1#comment-22139 Keith Fri, 08 Apr 2005 23:13:47 +0000 http://almaer.com/blog2/apache-beehive-pageflows-vs-spring-webflow#comment-22139 I forgot to mention: Spring Web Flow is used to power applications today at several large companies (notably a major bank and another large entertainment company.) It definitely didn't just appear out of nowhere, and that's a major reason why the feature-set is already so mature. I forgot to mention: Spring Web Flow is used to power applications today at several large companies (notably a major bank and another large entertainment company.) It definitely didn’t just appear out of nowhere, and that’s a major reason why the feature-set is already so mature.

]]> By: Keith http://almaer.com/blog/apache-beehive-pageflows-vs-spring-webflow/comment-page-1#comment-22138 Keith Fri, 08 Apr 2005 21:16:10 +0000 http://almaer.com/blog2/apache-beehive-pageflows-vs-spring-webflow#comment-22138 Dion, Speaking on behalf of the Spring Web Flow Team: - Spring Web Flow is immature in the sense we've only released a preview relase to this point (PR2 will be 4/11). However, the offering is quite mature in terms of feature-set, and in terms of quality on a united code, doc, and test front (as those who have reviewed it will attest to.) - We don't speculate on stuff thats not reality. It's a honest-to-good fact Spring web flow's core has no dependencies on any one web MVC framework. It's a fact we already provide Spring MVC and Struts integration, as well as Portlet integration. We don't speculate about what we feel, we speak facts backed up by working code. I agree - BEA and Beehive have expressed keen interest working with us after at TSSJS and we look forward to seeing the best of both worlds emerge. It's in everyone's best interest to provide _the best solution_, and that's our goal here. Cheers, Keith Dion,

Speaking on behalf of the Spring Web Flow Team:

- Spring Web Flow is immature in the sense we’ve only released a preview relase to this point (PR2 will be 4/11). However, the offering is quite mature in terms of feature-set, and in terms of quality on a united code, doc, and test front (as those who have reviewed it will attest to.)

- We don’t speculate on stuff thats not reality. It’s a honest-to-good fact Spring web flow’s core has no dependencies on any one web MVC framework. It’s a fact we already provide Spring MVC and Struts integration, as well as Portlet integration. We don’t speculate about what we feel, we speak facts backed up by working code.

I agree – BEA and Beehive have expressed keen interest working with us after at TSSJS and we look forward to seeing the best of both worlds emerge. It’s in everyone’s best interest to provide _the best solution_, and that’s our goal here.

Cheers,

Keith

]]>