David Nuescheler wrote: >> imo we need not request input validation. if you want to restrict, use >> the repository value constraints :-) > seriously: +1 > > anyway, i think we should not even consider a different level of validation > that could possibly conflict with what we have in the repository. > sling can use the nodetype definitions to do the validation before trying to > commit. > > if we have a usecase that goes beyond the validations we have in jcr then > we can engage in further discussions. the focus is on "use"-case not > "make-up"-case. > > i sure don't hope this is another case of "abstracting away from the repo" > and that's why we would like to introduce a whole new constraint framework > even for simple things such as "number in a range" or a "string that matches > a given regexp". > He, you're taking all the fun out of this discussion :) Now, I think it makes sense to have an additional validation mechanism on top of JCR. I guess with the node type definitions you can't handle all validation cases (like validating one field depends on the value of another one etc.). So we need these hooks.
It makes sense to leverage the validation information from the nodetypes, of course. And I also think that it makes sense to validate the input based on this information before a commit. So some sort of general service doing this would be great... Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
