[hibernate-commits] Hibernate SVN: r16727 - beanvalidation/trunk/validation-tck/src/main/resources.

[hibernate-commits at lists.jboss.org]

Author: hardy.ferentschik
Date: 2009-06-09 12:48:27 -0400 (Tue, 09 Jun 2009)
New Revision: 16727

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-06-09 16:47:42 UTC (rev 16726)
+++ beanvalidation/trunk/validation-tck/src/main/resources/tck-audit.xml	2009-06-09 16:48:27 UTC (rev 16727)
@@ -3,18 +3,6 @@
     xsi:schemaLocation="http://jboss.com/products/webbeans/tck/audit http://snapshots.jboss.org/maven2/org/hibernate/tck-utils-api/0.9-SNAPSHOT/tck-utils-api-0.9-20090220.134140-13-audit.xsd"
     name="JSR-303: Bean Validation" version="Revised Public Review Draft">
 
-    <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>An annotation is considered a constraint definition if its retention policy
@@ -166,7 +154,7 @@
         <assertion id="g">
             <text>It returns false if the value is not valid, true otherwise</text>
         </assertion>
-        <assertion id="h">
+        <assertion id="h" testable="false">
             <text>isValid implementations must be thread-safe</text>
         </assertion>
         <assertion id="i">
@@ -505,7 +493,7 @@
         </assertion>
     </section>
     <section id="4.1" title="Validator API ">
-        <assertion id="a">
+        <assertion id="a" testable="false">
             <text>Validator implementations are thread-safe</text>
         </assertion>
     </section>
@@ -678,7 +666,7 @@
         </assertion>
     </section>
     <section id="4.3.2" title="Custom message interpolation">
-        <assertion id="a">
+        <assertion id="a" testable="false">
             <text>A message interpolator implementation shall be thread-safe</text>
         </assertion>
         <assertion id="b">
@@ -694,7 +682,7 @@
         </assertion>
     </section>
     <section id="4.4.1" title="Examples">
-        <assertion id="">
+        <assertion id="a" testable="false">
             <text>The ValidatorFactory object is thread-safe</text>
         </assertion>
     </section>
@@ -749,10 +737,10 @@
     <section id="4.4.4.1" title="">
         <assertion id="a">
             <text>ValidationProviderResolver returns the list of Bean Validation providers available
-                at runtime and more specific- ally a ValidationProvider instance for each provider
+                at runtime and more specifically a ValidationProvider instance for each provider
                 available in the context</text>
         </assertion>
-        <assertion id="b">
+        <assertion id="b" testable="false">
             <text>Implementations must be thread-safe</text>
         </assertion>
         <assertion id="c">
@@ -876,11 +864,11 @@
         </assertion>
     </section>
     <section id="4.4.7" title="Usage">
-        <assertion id="a">
+        <assertion id="a" testable="false">
             <text>ValidatorFactory is a thread-safe object that should be built once per deployment
                 unit</text>
         </assertion>
-        <assertion id="b">
+        <assertion id="b" testable="false" >
             <text>Validator is thread-safe too and should be considered a lightweight object</text>
         </assertion>
     </section>