Ted Husted wrote:
> But, the Struts framework is really about about the Controller. You can
> use Actions as View Helpers, but if these views were going to be the
> basis of *my* application, I'd put the rendering engine in its own
> servlet.
Though, I suppose, if someone really, really doesn't want to forward
control,
another approach would be to use a "ViewAction" as a base class, and
then
call a render method at the end of perform.
public ActionForward render(
ActionMapping mapping, ActionForm form,
HttpServletRequest request, HttpServletResponse response)
throws IOException, ServletException;
If the rendering process needed to be tweaked, then the subclasses would
all inherit the changes on the next compile.
If you had more than one rendering technique, there could be more than
one base class in the hierarchy, and if the interfaces were compatible,
you could just change which one it extends.
If the base class extended org.apache.struts.actions.DispatchAction,
then you could also call the render method directly, and forego the
subclass.
This eliminates another pass through the forward guantlet, and the
ActionForm and ActionMapping would be unchanged.
If "render" were used an adapter, the rendering logic could be put
into another class, that render would call in the same way
other Actions call business logic, so that the whole thing is
not hopelessly bound to Struts.
An embarrassment of riches, this framework ;-)
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel +1 716 737-3463
-- http://www.husted.com/struts/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
