Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <23E8BF15-FCF3-4C57-B665-A990631D7F90@ruppconsulting.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: dev@struts.apache.org
From: David Rupp <david@ruppconsulting.com>
Subject: per-method validations for annotations
Date: Mon, 29 Jan 2007 20:43:43 -0700

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.

Regards,
David

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org