Hi Radu, I've briefly reviewed your SLING-2803 code and it looks quite good to me!
I'm wondering if it supports the following use cases: 1) Validating hierarchical structures Say I'm POSTing a small tree of resources rooted at /foo, can you validate for example that /foo/customer/email is present and valid according to an email validator? How about validating any property named "email" found somewhere within that posted tree? 2) Extensible types In the above example, can you also validate that the specified email is present in an external system, to which a custom OSGi service provides access? We might not need these features immediately, but IMO they should at least be supported at the API/code design level. -Bertrand
