Don, I think this is totally at odds with a lot of the things I've been
reading lately. Granted its been hard to separate the facts from the
noise lately (through no fault of anyone involved with the merger), but
even still...
Can I make a suggestion? Certainly for the sake of the users in both
communities, but also to be sure those doing the work are all on the
same page, I think it would be a good idea for someone to write up what
the plan actually is, and make sure everyone is on board with it. Maybe
I'm speaking out of turn and such a thing already exists, but I really
believe a lot of people are thinking this is just a Webwork rebranding,
with some additions taken from Struts, and if that isn't the case I
think it would be prudent to have a document than anyone can point to
and say "that's what we're doing, that's the plan!".
Frank
Don Brown wrote:
Gabe wrote:
I wanted to answer these two comments by Ted. Whether to bring XWork
is a very important decision to make ASAP, because it is about how we
define Struts Action 2.0.
Struts Action 2.0 = Webwork
- or -
Struts Action 2.0 = Webwork + XWork
While I'll let other XWork/WebWork folks weigh in on the XWork issue, I
want to quickly make the point that this equation is incorrect. The
original vision of Struts Action 2.0 started as Struts Ti. It was a
collaboration of Beehive, WebWork, and Struts folks looking to write a
simplified, Action 2 framework that leveraged the strengths of each.
The first Ti prototype was going to be built on XWork, but I ended up
just using WebWork itself since it did everything I wanted and was very
easy to build upon. Spring was included into the discussion and soon
"Clarity" was born with the idea of merging the four frameworks, however
that proved too big of task for those involved. Ted threw out the idea
to WebWork for their team to merge forces and work on Ti, and that's how
the merger started.
From the beginning, the goal was to create a project that simplified
the developers task of writing web apps though less configuration and
more modern features, and combining efforts is how we plan to accomplish
this. While yes, we might hold off on new fancy features for now so we
can get the first versions out quickly to the community, the goal was
not and has never been a simple "rebranding" of WebWork.
I'm sure you didn't mean it that way, but I wanted to take this
opportunity and correct a misconception that seems to be going on around
this project. Our goal is to create a new simpler, more feature-rich,
developer-oriented framework leveraging all we've learned from Struts,
WebWork, and other frameworks out there.
Carry on :)
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Java Web Parts -
http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
