UPDATE: To reflect the fact that the validators don't really use ajax, but rather javascript generation.

If you're like me and have checked out the Castle Project's trunk source tree (for exploration and to help learn a lot about how it works), it's really cool to grab the latest updates once a week or so.  It really shows how hard these guys are working on adding and improving these frameworks. 

Of particular interest in the update I did tonight were a lot of validators added to the trunk.  Even though Hammett is 2nd guessing some of the Castle Validator implementation, I've found it to be a good fit for my current project.  I hand-rolled a basic attribute-based validation engine very similar to this about 6 months ago (not all that hard), but the nice thing about using Castle's is the nice integration points it has with MonoRail.  I haven't played much with turning on the Ajax integration  javascript generation for the validators, but I definitely plan to and it's nice to know it's there.

So what's cool, is that I've already noticed a couple validators that were added to the trunk that I've already custom built in my current project, so the more "out of the box" components like these that are added, means less I have to hand-roll.  And perhaps at some point, I may even submit a few of my own if folks would find them useful.

So if you're serious about learning the inner workings of the Castle Project or just to help learn about it in general, I'd encourage you to grab the latest source and give it a look.  They have a ton of great sample and test projects included in the source which have really helped me ramp up on everything.

If you're new to Subversion, you'll want to download TortoiseSVN to check out the source code from their Subversion repository.