commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Ballard" <kball...@bcgi.net>
Subject [Validator] Validator usage with DispatchAction
Date Wed, 02 May 2007 13:31:27 GMT
I was looking at that this link
(http://struts.apache.org/1.x/struts-extras/dispatchValidator.html)
about using the "page" attribute when validating forms submitted for a
Struts DispatchAction so that only certain fields are validated when
submitting a form for a particular method of the DispatchAction. The
technique is recommended for use with wizard-like flows so the "page"
attribute refers to the sequence of the step in the flow. But what about
the case where you have grouped a set of logically related Actions into
a single DispatchAction (and they share the same coarse-grained
ActionForm) but there is no flow? Is it also recommended that you use
this technique in these sorts of cases? The major difference is that
there is no set sequence of steps (i.e. a user might only use a method
or two of the DispatchAction in a given use case) so the "page"
attribute just functions as a unique identifier of the validation. Is
this considered proper usage of Validator? Are there any problems with
this approach?

 

Thanks,

Ken

 




-----------------------------------------
The information contained in this e-mail message and any
attachments is confidential, and is intended only for the use of
the party to whom it is addressed. This message and any attachments
herein are subject to scanning and may be monitored at any time for
review.  If you are not the above-named intended recipient, you are
hereby notified that any dissemination, copying or disclosure of
this communication is strictly prohibited. If you have received
this communication in error, please notify Boston Communications
Group, Inc. immediately by replying to this message or by
telephoning (781) 904-5000, and destroy this message and its
attachments, without making any copy or distribution.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message