[
http://www.stripesframework.org/jira/browse/STS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Gunter resolved STS-72.
---------------------------
Resolution: Fixed
Fixed for 1.5. When validation info is loaded for a class, Stripes climbs the
class hierarchy checking each class for conflicts in the annotations. The
@Validate and @ValidateNestedProperties for a single property must be present
on only one element (getter, setter or field) in a single class. Annotations
from a subclass are preferred over those present in the superclass.
> Conflicting Validation annotations should generate errors
> ---------------------------------------------------------
>
> Key: STS-72
> URL: http://www.stripesframework.org/jira/browse/STS-72
> Project: Stripes
> Issue Type: Improvement
> Components: Validation
> Affects Versions: Release 1.0, Release 1.0.1
> Reporter: Jordan Reed
> Assignee: Ben Gunter
> Priority: Minor
> Fix For: Release 1.5
>
>
> Since I can add validate to both the getter and setter method I can do the
> following:
> @Validate(required=true)
> pubic void setFoo(String foo) {}
> @Validate(required=false)
> public String getFoo() {}
> Stripes chooses an arbitrary validation to use. This should generate an
> exception or at least a very loud log message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
