I think that is an awesome idea. There is still a lot of confusion in the Java Community on Struts versus Page Flows despite the fact that they are layered on each other and complementary technologies. I think by moving it into the Struts path it will continue to grow in conjunction with Struts. Any duplication of JSP tags, validation techniques, etc. will mold into one with the best implementation winning out. It will allow users to pick and choose by project as Page Flows become one way of implementing Struts instead of the either or that is present in the community today.
Even though today they are integrated technologies the genesis of PageFlows from BEA still has some history that is keeping developers from considering it in project architecture. There is a place for PageFlow architecture however it is not a choice of Struts versus Page Flows across the enterprise but should be a project by project consideration as is .Net versus Java/J2EE at many large corporations today. I think this change can be nothing but positive for both projects. Just my two cents Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -----Original Message----- From: Rich Feit [mailto:[EMAIL PROTECTED] Sent: Saturday, December 03, 2005 9:06 AM To: [email protected] Subject: Struts, WebWork, and Beehive Hi all, This mail involves a potentially big question about the future of Beehive; I'll try to keep it short, but if you're impatient, skip to the middle. :) Ted Husted and Don Brown of Struts have proposed merging WebWork into Struts: http://www.mail-archive.com/dev%40struts.apache.org/msg13815.html This is a big deal; see http://www.theserverside.com/news/thread.tss?thread_id=37794#192216 for starters. Following from the prototyping work that we did with "Struts Ti", they've included Beehive Page Flow as part of a Phase 2: > * Ti phase 1 = WebWork 2.2 + Struts 1.x compatibility library and migration tools > * Ti phase 2 = phase 1 + Commons Chain integration + Beehive's Page Flow + simplified annotations + quick development mode ** What this means is that most of the NetUI piece of Beehive would move into the Struts project -- refactored or rewritten to run on the core action framework that's being developed in Phase 1. ** The question for our community is, do we want to sign onto this? For my part, I am all for it. I think it would be good for Beehive (joining forces with our "big sibling") and it would be good for Struts (bringing in our toolability, annotation-based programming model, etc.). We're both Apache projects, and it seems like a natural move to make. What are your thoughts? Eddie and I will both be at ApacheCon along with several of the Struts committers, so any support/objections/questions/concerns you have before that will help us understand where the Beehive community stands on this. Thanks, Rich
