-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Sorin,
Did you specify the schema in the validation scenario as a custom schema by selecting the radio button "Use custom schema"? [...] yes
[...] 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. [...]
Do you mean, that ${ds}/${dsu} should be expanded by Oxygen to the schema url (and in my case it just does not), or that I have to create a distinct custom validation engine for every custom schema I want to use? In the latter case, it would be nice feature to map the custom schema to ${ds}/${dsu}. Thanks Stefan Am 01.07.2011 10:44, schrieb Sorin Ristache:
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: 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/
iEYEARECAAYFAk4NmXgACgkQ6m+l2LO+BGxRHACfZd85OqTdjfs6kRbKUhx9LuKL 82UAmgNX2RyltAf0F9gTLW4YuldsPaSW =RUxa -----END PGP SIGNATURE-----