On 5/3/06, Sean Gilligan <[EMAIL PROTECTED]> wrote:
I've taken a serious (but probably not long enough) look at WebWork, but
I haven't seen anything specific about what's coming with the
Struts/WebWork merger. Can someone provide information/links on this?
In the first phase, we're just repackaging the framework as an Apache
Struts product and resolving any licensing issues, so that it can be
distributed under the Apache License, without any encumbrances. We're
hoping to wrap phase 1 up by August. The SAF 2.0 release would be the
technical equivalent of WW 2.3.
There are other API changes being discussed for "phase 2",
* http://wiki.apache.org/struts/RoughSpots
but Job One is getting out a stable ASF release that we can start
using right away.
In looking at WebWork, it seemed to me that you are forced into much
more abstraction from HttpServletRequest etc. than we really need for
the blog UI and that it would be a much bigger change to the existing code.
Actually, acquiring the HttpSerlvetRequest is one line of code, just
like anywhere else.
{{HttpServletRequest request = ServletActionContext.getRequest();}}
We do encourage a higher-level of abstraction, but everything you
would need is provided through the ServletActoionContext, if that's
what you need to do.
For more see
* http://confluence.twdata.org/display/WW/How+can+I+get+the+HttpServletRequest
It would be great if someone that knows WebWork (or SAF 2.0?) could take
a look at my proposal and provide some guidance into how WebWork/SAF2
could be used to do something similarly lightweight. If not, do we have
the resources (I'm willing to help, but will be of much less value) to
do a WebWork/SAF2 implementation of the blog UI?
I'm trying to wrap-up a preliminary pass on the SAF2 wiki right now,
but as soon as that is done, I will take a close look at the proposal.
-Ted.
