> If you looked at the Struts Ti proposal, you'd see > that the goal was to start > developing advanced features to dramatically simplify > development. The whole > reason we looked at WebWork in the first place is we > wanted a solid foundation > so that we could focus on features. > > With the merger comes an opportunity for the WebWork > developers primarily to > clean up the API and rethink a few things. However, > the API discussions we've > had so far make it clear these are API cleanups, not > fancy new features.
I must disagree. Bob and Patrick's first cut at the API is a NEW API, not a cleanup. It's very different from an end-user perspective, even if we could implement it with what we've got. > > Therefore, to state once again, our goal in this > first phase is to keep the > feature changes, the end user stuff, minimal so that > we can get a solid release > out quickly. The second phase focuses on fancy new > features like annotations, > zero config, quick deployment, or whatever else we > want to try. > Well, that's why I asked, because these are not minimal changes to the end user API. > This is why Ted pointed out the current Struts Action > 2 proposal is really just > a clarification of the original Struts Ti proposal. > --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=29563&messageID=57555#57555 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
