|Re: Custom XML Validation on top of schema validation [message #174459 is a reply to message #174152]
||Fri, 14 July 2006 14:57
| Brian Jakubik
Registered: July 2009
Here is what I ended up doing, my runtime side has rules validation that i
need, and I wanted to try to reuse that, I ahve my validator action ...
setup very similar to the XML validator, and instead of using the XML one, I
use mine and return the XMLValidationreport with my errors in it.
Works as I would like it to, although I am implementing and using some
internal/provisional classes, but it is experimanetal for now.
<email@example.com> wrote in message news:firstname.lastname@example.org...
> Hi Brian,
>>Now I want to nix the XMLValidator and do my own thing here. My question
>>this, what should I do from here, do I get a DOM and check the things
>>that, Is there a way to extend the SAX parse to catch it, or something
>>I dont know about... I have never used SAX before and am somewhat new to
>>the validation thing.
> You can use either method. Here is a simplified overview. DOM is useful if
> you need to build the entire model before validating, as is the case with
> WSDL. For example, if you want to check that references amoung elements
> are correct. SAX is lighter weight than DOM and is useful if you want to
> check the current element. For example, if you want to implement naming
> convention checks where all you're checking is the name of the current
> You can find more information about DOM and SAX from the Xerces site 
> and from the W3C .
>  http://xerces.apache.org
>  http://www.w3.org/DOM/
Powered by FUDForum
. Page generated in 0.02592 seconds