In "Ajax Form Validation Using Spring and DWR," I presented a design to use Ajax to perform client-side validation by invoking an application's server-side validation logic. The whole point was to easily leverage validation logic on the server to prevent duplication of code, to reduce the time and cost of development and maintenance, and to enhance the usability of a web application. Few non-trivial software designs get it right the first time. This design has been running in production systems for over a year (its publication is approaching the ten-month mark), and has shown some limitations. This article discusses the emerged limitations and then presents an improved design that not only addresses the limitations but provides added functionality. Conceptually, the two designs are very similar, and a familiarity with the previous article, or working knowledge of Ajax, DWR, and the Spring Web MVC framework, are assumed.