You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@tomee.apache.org by bu...@apache.org on 2012/08/25 12:59:29 UTC

svn commit: r830105 - in /websites/staging/openejb/trunk: cgi-bin/ content/ content/dev/writing-validation-tests.html

Author: buildbot
Date: Sat Aug 25 10:59:28 2012
New Revision: 830105

Log:
Staging update by buildbot for openejb

Modified:
    websites/staging/openejb/trunk/cgi-bin/   (props changed)
    websites/staging/openejb/trunk/content/   (props changed)
    websites/staging/openejb/trunk/content/dev/writing-validation-tests.html

Propchange: websites/staging/openejb/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Aug 25 10:59:28 2012
@@ -1 +1 @@
-1377260
+1377261

Propchange: websites/staging/openejb/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Aug 25 10:59:28 2012
@@ -1 +1 @@
-1377260
+1377261

Modified: websites/staging/openejb/trunk/content/dev/writing-validation-tests.html
==============================================================================
--- websites/staging/openejb/trunk/content/dev/writing-validation-tests.html (original)
+++ websites/staging/openejb/trunk/content/dev/writing-validation-tests.html Sat Aug 25 10:59:28 2012
@@ -175,8 +175,8 @@ conditionally added to the <em>chain</em
 
 <ol>
 <li>Internally ValidateModules uses the <a href="https://github.com/apache/openejb/tree/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/config/ValidateModules.java"><em>AppValidator.validate()</em> method</a></li>
-<li>This method then performs validation using a number of rules. <em>A
-validation rule/s is represented by a class implementing ValidationRule</em>.
+<li>This method then performs validation using a number of rules. _A
+validation rule/s is represented by a class implementing ValidationRule.
 In fact, all the classes checking the validation rules , extend
 ValidationBase, which further implements ValidationRule.</p>
 
@@ -185,8 +185,7 @@ ValidationBase, which further implements
 
 <p>The <em>list of rules</em> being executed can actually be found in the following
 method of <a href="https://github.com/apache/openejb/tree/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/config/AppValidator.java">AppValidator</a>
-1. The above rules are then executed one by one<div class="snippet">:id=code2|url=openejb3/container/openejb-
-core/src/main/java/org/apache/openejb/config/AppValidator.java|lang=java}</p>
+1. The above rules are then executed one by one</p>
 
 <ol>
 <li>Each module has an attached ValidationContext , which maintains a list of
@@ -254,7 +253,7 @@ message key, then that key should exist 
 
 <ol>
 <li>The first thing to note is that we are running the test using our
-own custom runner i.e. @RunWith(ValidationRunner.class). This runner
+own custom runner i.e. <code>@RunWith(ValidationRunner.class)</code>. This runner
 ensures that the keys we are testing, actually exist in the
 messages.properties file. It does a lot more, as we shall see later    </li>
 <li>The test method</li>
@@ -279,7 +278,7 @@ then the test fails.
 <p>The test must cause a Validation Failure otherwise the test framework does
 not get invoked. For example, in the above code, a Key of type WARNING is
 being tested, however the test is purposely being failed by putting an
-@AroundInvoke around the method with zero arguments<div class="note">}</p>
+<code>@AroundInvoke</code> around the method with zero arguments</p>
 
 <ol>
 <li>Once you have written the test and successfully run it, you now need to
@@ -325,7 +324,7 @@ found, then the Runner throws and except
 being allowed to run.</li>
 <li>Sometimes you want to write a test where you do not want any
 ValidationFailureException to be thrown, in those scenarios, simply
-annotate your test with @Keys and do not specify any @Key in it<div class="info">}</li>
+annotate your test with @Keys and do not specify any @Key in it</li>
 </ol>