Jim,
Thanks for the input. I was leaning that way but was concerned about
duplicating the code necessary to render the view in several controllers.
How do you handle this?
One approach I considered using is having 2 controllers: one which handles
mid to backend functionality (business logic, persistence, etc.) and another
which renders the view. I would then chain the controllers using a Forward
view (operates like a JSP forward instead of redirect). This would allow me
to have only one bit of code for rendering the view while business functions
could be handled in multiple controllers. Does this seem sound? Is there
anything I'll need to do to make my Forward view work other than the
following?
In ForwardView:
RequestDispatcher rd =
vctx.getServletContext().getRequestDispatcher(resourcePath);
rd.forward(vctx.getRequest(), vctx.getRealResponse());
instead of the Redirect view's:
vctx.getRealResponse().sendRedirect(result);
John-Mason Shackelford
Software Developer
NCS Pearson - Measurement Services
2510 North Dodge St.
Iowa City, IA 52245
319-354-9200x6214
[EMAIL PROTECTED]
****************************************************************************
This email may contain confidential material.
If you were not an intended recipient,
Please notify the sender and delete all copies.
We may monitor email to and from our network.
****************************************************************************
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
[INVALID FOOTER]
