From 49e3882ae6552a05fd2cd56e7ecd560d3f795ece Mon Sep 17 00:00:00 2001 From: James Moger Date: Mon, 25 Mar 2013 22:49:16 -0400 Subject: Documentation --- src/site/tools.mkd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/site/tools.mkd') diff --git a/src/site/tools.mkd b/src/site/tools.mkd index 6d8c348..8c02a12 100644 --- a/src/site/tools.mkd +++ b/src/site/tools.mkd @@ -20,16 +20,16 @@ If you do not have or do not want to annotate your existing model classes, you c Iciql can validate your model classes against your database to ensure that your models are optimally defined and are consistent with the current table and index definitions. Each `com.iciql.ValidationRemark` returned by the validation has an associated level from the following enum: -%BEGINCODE% +---JAVA--- public static enum Level { CONSIDER, WARN, ERROR; } -%ENDCODE% +---JAVA--- A typical validation may output recommendations for adjusting a model field annotation such as setting the *maxLength* of a string to match the length of its linked VARCHAR column. ### Sample Model Validation using JUnit 4 -%BEGINCODE% +---JAVA--- import static org.junit.Assert.assertTrue; import java.sql.SQLException; @@ -92,4 +92,4 @@ public class ValidateModels { System.out.println(message); } } -%ENDCODE% \ No newline at end of file +---JAVA--- \ No newline at end of file -- cgit v1.2.3