From a7c3d1ed2fc2e50878b5fadfdfc7bab6ba686228 Mon Sep 17 00:00:00 2001
From: Keith Donald <kdonald@vmware.com>
Date: Mon, 2 Mar 2009 14:57:36 +0000
Subject: [PATCH] mvc compat

---
 ...DefaultSpringMvcValidationFailureMessageCodesFactory.java | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/spring-binding/src/main/java/org/springframework/binding/validation/DefaultSpringMvcValidationFailureMessageCodesFactory.java b/spring-binding/src/main/java/org/springframework/binding/validation/DefaultSpringMvcValidationFailureMessageCodesFactory.java
index 59b86cb4..16d12128 100644
--- a/spring-binding/src/main/java/org/springframework/binding/validation/DefaultSpringMvcValidationFailureMessageCodesFactory.java
+++ b/spring-binding/src/main/java/org/springframework/binding/validation/DefaultSpringMvcValidationFailureMessageCodesFactory.java
@@ -20,6 +20,11 @@ package org.springframework.binding.validation;
  * ${failureMessageCodePrefix}.${constraint}
  * </pre>
  * 
+ * Notice how the constraint comes after model/property qualifiers in the default algorithm, while the original Spring
+ * MVC algorithm has the constraint come before. The default algorithm is believed to be more object oriented and
+ * generally preferred. The Spring MVC algorithm is supported for backwards compatibility and consistency with existing
+ * Spring MVC web applications.
+ * 
  * @author Keith Donald
  */
 public class DefaultSpringMvcValidationFailureMessageCodesFactory extends ValidationFailureMessageCodesFactory {