Pilgrim, Peter wrote:
If I understand you rightly the traditional `RequestProcessor'
derived process flow, namely
ActionServlet => RequestProcessor => Action => View
is gone to be replaced by the WebWork / X Work processing
chain.
If someone has invested in Commons Chain command will they
be able to quick migrate or directly use Struts 2.x
engine.
Is there an equivalent of the `RequestProcessor' concept in the
webwork/xwork?
There isn't directly, and this was one of the first additions I made to WebWork
when I started Struts Ti. In WebWork, the servlet dispatcher does everything
prior and including identifying the Action, then hands it off to the interceptor
chain. My code in Struts Ti replaced this with a servlet that hands off to a
RequestProcessor, which used Commons Chain to perform all the preprocessing.
I plan to be adding this back in shortly after we import the WW code base.
I'd say pick up the WebWork in Action book
(http://www.manning.com/books/lightbody) written by the
primary WebWork
developers themselves. Of course once Struts in Action 2ed
comes out, it will
be better ;)
Has anyone writen a WebWork introductio guide for experienced
Struts users yet?
Nope, and no offense to Patrick, but web documentation wasn't a strong point of
WebWork...now this new WebWork in Action book on the other hand... :)
Rest assured, this will be a key requirement before we create the first Struts
Ti release.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
