I'd like to see: 1. Model validation
2. Schema generation based on Validation Attributes 3. Client-side validation using jQuery or Prototype or whatever >From what I know (and please correct me if I'm wrong), we currently do #1 & #3. NH does #1 & #2. As I see it, I have two options: 1. Get with the NH Validation folks, and see what it would take to merge the two codebases, or 2. Make our Validation compliant with the NH Schema generation process. Also, didn't someone mention the idea of a standardized validation interface, kinda like the Common Service Locator interface? Did I completely mis-remember that? Thoughts? -rb--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
