|
next
|
Subject: Re: XML Schema - extend then restrict type gives validation error Author: Andy Galvan Date: 02 Oct 2007 03:28 PM
|
Thanks, Alberto. I've moved my new schema into production, accepting that I'll have to select a custom validator each time I need to validate. I figure this will be fixed some time soon.
Now onto my next problem... I'm developing a new XSLT and want to validate my output. When using Stylus Studio, under Scenario Properties, Validation, the built in validator doesn't work - this I already know. But, when I try to "Use custom validator", it does not allow me to enter a schema. Not allowing this to stop me, when I try to run my XSLT (all still within the SS development environment) and validate against my schema, I get the following error (which references my output file):
Running custom validation engine .NET XML Parser...
Command line failed:
C:\PROGRA~1\STYLUS~4\bin\Custom Validation Engines\XmlValidator\XmlValidator.exe "g:\ag\WO63219.AG\20071001T14_qs.xml" auto
Initial Directory:
(null)
Error Message: The system cannot find the file specified.
I think I should still be allowed to enter a schema, when I choose a custom validation engine. I have tried selecting the build-in validation engine, entering the schema, and then changing to a custom validation engine. This leaves my schema in a non-enterable "Validate against these schemas" text box, but still gives me the above error.
I'm now running with the 2007 Professional Suite, build 894m.
Short of saving my XSLT output to a file, re-loading it, associating it with my schema, selecting a custom validation engine and run... is there another way around this nuisance?
|
|
|
|