Hi David, re the use case I still got this one I brought up a while ago: catching spam comments on a blog.
However, for this use case I do not think I need the validator functionality typically offered in web frameworks (like checking for empty strings or stuff like that). I would like to intercept POSTs to the microjax servlet with some custom logic (in a script). If that is possible all the simpler validation stuff (like checking for required values) can be implemented (by an application writer) as well if someone wishes to do so. When this was first discussed I think the result was to "implement the POST script". But I would like to extend the behavior of the PostServlet without having to reimplement everything it does. That would be something like "implement the POST script (do some validation there) and pass on the request to the POST servlet or not (depending on the validation)". Cheers Michael On 12/6/07, David Nuescheler <[EMAIL PROTECTED]> wrote: > > hi carsten, > > > hehe ;) > > 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. > i am all for a general "validate()" hook. > (... to take care of the "dream"-case. ;) ) > > > 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... > excellent. then all the general cases from xss to integer validation > can easily be taken care of via regular nodetype definition. > > regards, > david > -- Michael Marth, http://dev.day.com
