It's something I actually will be needing in the near future. If no one
beats me, I'll probably take a look at the patch (late?) next week.
David
Laurie Harper wrote:
David Rupp wrote:
Hi, all.
I've submitted a patch to the XWork project (issue XW-470) that
enables per-method validations when using annotations. This is, IMO,
an improvement over the current behavior, with which all validations
are attached to the class, and *all* fire when *any* method is
executed. Since validation annotations, by definition, *must* be
defined on a specific method, it seems more reasonable to expect that
the validations defined on a given method would fire when - and only
when - that method is executed.
I have a specific need for this behavior on my current project, but
I'd rather not be in the position of maintaining a forked version of
XWork just for it. I'd love it if some of the folks from this group
could take a look at my patch (included on the issue) and let me know
how it can be improved, assuming I'm not the only one who would like
to see this behavior implemented.
+1, since we've already had at least one user expecting it to work like
this and it would certainly make the framework more flexible. I haven't
looked at the patch but I'd like to see this functionality added, in
some form.
L.
---------------------------------------------------------------------
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]
