The future of XWork with the merger

I opened up a message thread a while ago on the struts mailing list about whether we should move XWork over to struts as well as webwork. That thread can be found here:

http://thread.gmane.org/gmane.comp.jakarta.struts.devel/37945

Another thread was brought up here as well:
http://thread.gmane.org/gmane.comp.jakarta.struts.devel/38995/focus=38995

I raise this because a lot of issues seem to be coming up in the merger that require that we examine the relationship of XWork and Struts 2 moving forward. For example, pluggability of expression language and annotation driven actions are both issues that really apply to changing the XWork codebase rather than the webwork one.

I think XWork should move over with Webwork and as two parts of Struts 2 that exist similarly to how XWork and Webwork relate now, something like "Struts 2 Web" and "Struts 2 Core". They said this has to be an issue discussed by the XWork community, so I thought I would post it here.

In any case, Struts 2 developers and XWork developers alike need to determine what the relationship will be moving forward. Will Struts 2 add features that would normally be added to XWork to the Struts 2 base blurring the lines that existed between Webwork and XWork or will they submit those changes to the XWork codebase? Would XWork simply copy features that existed in Struts to XWork, because they were good and were not web dependent? Would Struts document XWork documentation as if it were its own like webwork sort of does now or would it point its developers to XWork documentation? etc. etc. etc.

Anyway, just wanted to start the discussion here to see what people think.

Gabe
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=26295&messageID=51749#51749

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]