Hello, Did you specify the schema in the validation scenario as a custom schema by selecting the radio button "Use custom schema"? If yes the variable ${ds} or ${dsu} from the command line of the custom validator should be replaced with the file path or URL of the schema from the scenario. If ${ds}/${dsu} is not expanded when you run the scenario please post here the output that is displayed in the Info view when you validate the XML document. What is the command line of the validator specified in Preferences -> Editor -> Custom Validation Engines? What is the URL of the custom schema that you set in the validation scenario? Regards, Sorin Stefan Krause wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I had configured a custom validation engine. It works fine if I invoke it with the validation button and a detected schema (referenced by <?oxygen?>-PI). If I use the same custom engine from inside of a validation scenario with a custom schema url, validation fails because ${ds}/${dsu} are not set.
How can I pass the custom schema URL from the validation scenario to the validation engine? I suppose there is an other editor variable, but I couldn't find it.
Thanks,
Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4MoAoACgkQ6m+l2LO+BGxZ+wCgyzRZs7eQcl+HBh04M3Zk/NbR NEAAnjd6ELP7rhQRG+GIUwAJ9BMks7Kl =XdDy -----END PGP SIGNATURE-----