I don't think I can utilise the first approach as I am always using the same
action (via the html form's submit).

The second approach may do the trick - though I'll have to start using the
validator (rather than the default stuff in the action form).

Thanks for your help,

Paul

-----Original Message-----
From: Bailey, Shane C. [mailto:[EMAIL PROTECTED]
Sent: 30 July 2003 15:00
To: 'Struts Users Mailing List'
Subject: RE: DispatchActions - using form validation for only some
methods



Not sure if anybody answered you question or not yet but there are a couple
things you can do...

1. Have many action mappings to one DispatchAction.  
<action path="/a" parameter="subtask" type="my.Dispatch" ...> ... </action>
<action path="/b" parameter="subtask" type="my.Dispatch" ...> ... </action>

link to each as "/a.do?subtask=method1" and "/b.do?subtask=method2" and then
do validation per action and not per form.

The other alternative suggested by Robert Taylor, which, once set up, is
pretty slick but involves a little extension to how validator works:
http://marc.theaimsgroup.com/?t=105352600600007&r=1&w=2





-----Original Message-----
From: Paul McCulloch [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 30, 2003 7:59 AM
To: 'Struts Users Mailing List'
Subject: DispatchActions - using form validation for only some methods

Hi,

I've just moved to using dispatch actions from my own implementation of
something similair to relay actions. One facility my implementation gave me
was to have the form validated when some actions were called, and not
validated for other actions (at the expense of a bloated struts-config.xml).

Using dispatch actions I am now explicitly calling the form's validation for
those methods that require a validated form:

        ActionErrors errors = form.validate(mapping, request);
         if(!errors.isEmpty()) {
             saveErrors(request, errors);
             return new ActionForward(mapping.getInput());
        }

Is there a better way of achieving this?

thanks,

Paul


**************************************
Axios Email Confidentiality Footer
Privileged/Confidential Information may be contained in this message. If you
are not the addressee indicated in this message (or responsible for delivery
of the message to such person), you may not copy or deliver this message to
anyone. In such case, you should destroy this message, and notify us
immediately. If you or your employer does not consent to Internet email
messages of this kind, please advise us immediately. Opinions, conclusions
and other information expressed in this message are not given or endorsed by
my Company or employer unless otherwise indicated by an authorised
representative independent of this message.
WARNING:
While Axios Systems Ltd takes steps to prevent computer viruses from being
transmitted via electronic mail attachments we cannot guarantee that
attachments do not contain computer virus code.  You are therefore strongly
advised to undertake anti virus checks prior to accessing the attachment to
this electronic mail.  Axios Systems Ltd grants no warranties regarding
performance use or quality of any attachment and undertakes no liability for
loss or damage howsoever caused.


---------------------------------------------------------------------
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]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to