The current validation API assumes that validation is a feature of a reader. That's not really what we want here, exactly, and I'm not sure how to get there. We have a StaX stream, and a portion of the events on it should correspond to a schema. Unless we have an xsd description of the soap envelope and such, I'm not sure what to expect here.
- Design problem with schema validation Benson Margulies
- Re: Design problem with schema validation Daniel Kulp