I'm not arguing against annotations, only saying that per-method
valdidations are supported.
One workaround would be to let the validation.xml include another
validation.xml. I haven't tried, but this might already be possible
using XML entities.
But, again, the annotation support would also be
Yes, but that requires seperate validations config per method - even if
they are identical.
Take a dumb example. . .suppose you have an action with simple methods:
load
create
update
delete
Perhaps you have the same validation on create and update, but do not
want them to execute on load and
Per-method validations are supported, using the convention
* ActionClass-actionMethod-validation.xml
This approach doesn't work with "dynamic method invocation" though
(the WW ! notation), because of the way DMI is implemented. Per method
validation does work with wildcards, though.
-Ted.
On 1
That's would be really usefull...
I am waiting too, If I could heap in something...
Thank's,
André Faria
David H. DeWolf escreveu:
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
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 w
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 e
