Donnie Hale wrote: > Well, as I've said, I certainly understand that point of view. I probably > lean that direction, if not just for the sake of clarity of responsibility. > But from a pure flexibility point of view, requiring forwarding is > constraining.
Forwarding is not required. Another approach would be a base VelocityAction that did whatever the VelocityServlet would do. If the Action returns null, the ActionSerlvet is satisifed. But to get best use out of the framework, a view rendering system that maps to an URI, and can access the Message Resources, is optimal. This could be used as a drop-in replacement where Struts developers now use JSPs. The Struts tag extensions are coupled with JSPs, but everything else in the framework is neutral. There is a premise is that the view-rending system can be accessed via a URI, and any system that does this will work as well as (or along with) JSPs. If I had a couple of PDF's to render, I'd probably use a PDFAction. If the whole application were PDFs, then I would probably go with a separate PDF servlet. In practice, there would probably not be any real difference between the two. Just a matter of where you want to park the code. -- 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]>
