Why did they make it tough to process an action on your own?

["Steel, Toby" <To...@CIBC.com>]

If one jsp requires many action.do ActionForward results be included on a
single page,
one used to use ActionServlet.processActionPerform (among other methods)
to preprocess the request so that each subsection of a main page could
be generated by the result of an Action.

This used to (Struts 1.0) be the workaround for the ineffective
<jsp:include page="/MyAction.do"/>

Now it seems (Struts 1.1beta1), I have to do all this work myself, from
within my ActionServlet.
[I think Ted Husted had a sample method called invokeAction( path, request,
response)
in one of his online examples]

***Why were all the 'processXXX' methods removed from ActionServlet?***

Using all the new Config stuff works well enough. I have to create my own
instance of the Action class, and manage form population and validation
myself. 
But it's a bit of a pain when the code used to be there and now it's gone.

Does this go against the framework?
------------------------------

On a related note, we are encouraged to use the
ApplicationConfig.findActionConfig() methods rather
than ActionServlet.findMapping() [Deprecated]. Yet Action.execute() still
takes ActionMappings rather
than ActionConfigs. Why? Or is this an oversight?



Toby Steel


 



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>