Simplest solution for now is to instantiate a SAX parser yourself, 
configured to do Schema validation, wrap a SAXSource around it and pass 
that to Xalan.

Alternatively, you could try our XSLT 2.0 prototype code in the "xslt20" 
branch of the CVS repository. This is still considered experimental; not 
all 2.0 features are supported yet, and performance tuning still needs to 
be done. (Though schema validation itself is a hugely expensive process 
right now, and obviously we don't have any control over that.)

______________________________________
Joe Kesselman  / IBM Research

Reply via email to