11:52 a.m.
Author: hardy.ferentschik
Date: 2009-05-18 12:52:40 -0400 (Mon, 18 May 2009)
New Revision: 16589
Modified:
beanvalidation/trunk/validation-tck/src/main/resources/tck-audit.xml
Log:
Modified: beanvalidation/trunk/validation-tck/src/main/resources/tck-audit.xml
===================================================================
--- beanvalidation/trunk/validation-tck/src/main/resources/tck-audit.xml 2009-05-18
14:11:08 UTC (rev 16588)
+++ beanvalidation/trunk/validation-tck/src/main/resources/tck-audit.xml 2009-05-18
16:52:40 UTC (rev 16589)
@@ -1,11 +1,84 @@
-<specification
- xmlns="http://jboss.com/products/webbeans/tck/audit"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://jboss.com/products/webbeans/tck/audit
http://snapshots.jboss.org/maven2/org/hibernate/tck-utils-api/0.9-SNAPSHO...
- name="JSR-303: Bean Validation"
- version="Revised Public Review Draft">
+<specification xmlns="http://jboss.com/products/webbeans/tck/audit"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://jboss.com/products/webbeans/tck/audit
http://snapshots.jboss.org/maven2/org/hibernate/tck-utils-api/0.9-SNAPSHO...
+ name="JSR-303: Bean Validation" version="Revised Public Review
Draft">
- <section id="2" title="Bean definition">
+ <section id="2" title="Constraint definition">
+ <assertion id="a">
+ <text>Constraints are defined by the combination of a constraint
annotation and a list
+ of constraint validation implement- ations</text>
+ </assertion>
+
+ <assertion id="b">
+ <text>The constraint annotation is applied on types, methods, fields or
other constraint
+ annotations </text>
+ </assertion>
</section>
+ <section id="2.1" title="Constraint Definition">
+ <assertion id="a">
+ <text>A constraint on a JavaBean is expressed through one or more
annotations</text>
+ </assertion>
+ <assertion id="b">
+ <text>An annotation is considered a constraint definition if its
retention policy
+ contains RUNTIME and if the annotation itself is annotated with
+ javax.validation.Constraint</text>
+ </assertion>
+ <assertion id="c">
+ <text>Constraint annotations can target any of the following
ElementTypes: FIELD,
+ METHOD, TYPE, ANNOTATION_TYPE</text>
+ </assertion>
+ <assertion id="d">
+ <text>If a constraint definition is not valid, a
ConstraintDefinitionException is raised
+ either at validation time or when the metadata is requested</text>
+ </assertion>
+ <assertion id="e">
+ <text>Applying a constraint annotation to an incompatible type will
raise a
+ UnexpectedTypeException</text>
+ </assertion>
+ </section>
+
+ <section id="2.1.1" title="Constraint definition
properties">
+ <assertion id="a">
+ <text>A constraint definition may have attributes that are specified at
the time the
+ constraint is applied to a JavaBean.</text>
+ </assertion>
+ <assertion id="b">
+ <text>annotation elements starting with valid are not
allowed</text>
+ </assertion>
+ <assertion id="c">
+ <text>Every constraint annotation must define a message element of type
String</text>
+ </assertion>
+ <assertion id="d">
+ <text>Every constraint annotation must define a groups element that
specifies which
+ processing groups the constraint definition is associated
with.</text>
+ </assertion>
+ <assertion id="e">
+ <text>The default value for the groups element must be an empty
array.</text>
+ </assertion>
+ <assertion id="f">
+ <text>If no group is specified when declaring the constraint on an
element, the Default
+ group is considered declared. </text>
+ </assertion>
+ </section>
+
+ <section id="2.2" title="Applying multiple constraints of the same
type">
+ <assertion id="">
+ <text></text>
+ </assertion>
+ <assertion id="">
+ <text/>
+ </assertion>
+ </section>
+
+
+
+ <!--
+ <assertion id="">
+ <text></text>
+ </assertion>
+ -->
+
+
+
</specification>