Even I think a wrapper on commons validation would be required in this sort of situation. Where the validations are fired on basis of a certain filter.
-----Original Message----- From: Dave Newton [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 9:58 PM To: Struts Users Mailing List Subject: Re: Help on Validation Scott Van Wart wrote: > Can you give an example? I'm still not completely positive I know > what the problem is, and if you really need this kind of complexity. I think he was asking if there was a way to declaratively define validations based on runtime dynamics, like the user name. This strikes me as a fantastically bad idea, since 'declaratively' and 'runtime dynamics' are kinda... diametrically opposed. I think that either a) the problem needs to be re-stated to fit in to the existing framework, or b) a different framework (possibly hanging off of commons-validation or possibly even the Struts wrapping of same) should be used. That said, I'll be interested in hearing other opinions as this might be a generally-useful tool (role-based validations would be useful to me and I'd like to see how others might implement that as a bag on top of the existing framework.) Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] MASTEK "Making a valuable difference" Mastek in NASSCOM's 'India Top 20' Software Service Exporters List. In the US, we're called MAJESCOMASTEK ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from all computers. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
