On 3/30/06, Gabe <[EMAIL PROTECTED]> wrote: > > Don, > > I was refering to phase I really, whether the starting point is Webwork or > Webwork + XWork.
I think Don is saying that it would be helpful to see a concrete proposal from the XWork developers that outlines what they would like to do. Once the set of XWork developers weigh in, we can continue the discussion. But, it is not appropriate for us to have the discussion here. We have no idea of how many XWork developers are following this thread. The starting point is the XWork community. It's interesting to note that Struts Action 1.3 has a similar dependency on Commons Chain. The XWork dependency is more extreme, but it is the same sort of thing. For Commons Chain, we chose to set it up as an independant project in the Jakarta Commons, so that it would be available to other projects too. Of course, we did the same thing with a great number of Action 1 dependencies, like BeanUtils, Validator, and so on. I'm aware that at least one other project is using XWork, and if it came out from under the WebWork shadow, them other projects might find it useful too. Even just here, Craig has mentioned that we might be able to use XWork Interceptors as part of Shale. If we tightly bind XWork to Action2, it may make it easier for Action 2 to use, but it would make it correspondingly harder for for other projects to use XWork. But, again, the place to have this conversation is at OpenSymphony, where the XWork community can fully participate. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
