On Tue, Aug 11, 2009 at 3:15 PM, Martin Cooper<mart...@apache.org> wrote: > OK, here's a question that's been on my mind for a while. Why is it that, > for almost every S2 release, we need to make changes to something as core as > XWork? Why isn't XWork stable enough by now that we don't have to be > changing it all the time? > > It's often bothered me that we always seem to need to wait for an XWork > release, not so much because of the wait, but because we seem to be so > dependent on constant change in that library. What's up with that? That is > what seems to be the real issue here.
This is exactly my point. XWork is such a core part of what Struts 2 is that it shouldn't be separate. Any non-trivial change to Struts 2 involves changes to XWork and I don't see that changing anytime soon. By forking XWork, we can a) bring core Struts 2 code into the project where it belongs and b) still leave it available for other users in OpenSymphony. Don --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
