The newest version of the Struts mailreader sample app shows a best
practices approach to just what you describe.
Take a look at that and see if you might be able to do the same.
(Specifically, look at the paths for Edit* and Save*)
HTH
--
James Mitchell
On May 4, 2006, at 9:40 AM, Mulligan, Scott H wrote:
I just started playing with the commons-validator and came across a
problem with how I have my Struts application structured. I am using
dispatch actions that have "load" and "save" methods. In the "load" I
retrieve the reference data needed to build the page and then
forward to
the jsp page. In the "save" method I process the form data.
My problem is that the validation is defined at the action level in
the
struts-config file. Therefore, my validation fails before I even
have a
chance to render the page. Do I need to separate the "load" and "save"
methods into different actions or is there a better way to handle
this?
Thanks in advance for any advice you can provide.
Scott Mulligan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
