Page 1 of 1
Problem validating XSL
Posted: Mon Jul 14, 2008 8:07 pm
by walker@amigos.org
when I attempt to validate an XSL stylesheet in Oxygen 9.3, I get the following message.
"SystemID: \\fs1\users$\walker\EAD\BakaYaro.xsl
Description: The transformer Saxon9B is not available anymore. Please reconfigure the transformation scenario."
When I go to validate the transformation scenario I see that the scenario is set to Saxon-B9.0.0.6
Applying the transformation scenario works, but the validation of the XSL gets the aforementioned message.
Bill Walker
Re: Problem validating XSL
Posted: Tue Jul 15, 2008 12:05 pm
by sorin_ristache
Hello,
The version of Saxon 9B changed in Oxygen version 9.3. Version 9.3 comes with Saxon B 9.0.0.6 but if you had Saxon-9B set in the option XSLT 2.0 Validate with (Options -> Preferences -> XML -> XSLT/FO/XQuery -> XSLT) which was the default value in version 9.2 then this option will switch in version 9.3 to the value JAXP instead of Saxon-B 9.0.0.6. We will fix the problem in the next version. Please go to Options -> Preferences -> XML -> XSLT/FO/XQuery -> XSLT and select the value Saxon-B 9.0.0.6 for the option XSLT 2.0 Validate with or press the button Restore Defaults.
Regards,
Sorin
Re: Problem validating XSL
Posted: Wed Sep 17, 2008 3:22 pm
by hschmitt
This worked for me, but I cannot configure Extensions for my validation scenario.
Can I do it somehow manually / on file basis?
Re: Problem validating XSL
Posted: Wed Sep 17, 2008 3:33 pm
by sorin_ristache
Hello,
The extensions of the validator must be added to the validation scenario using the Extensions button of
the dialog for editing a validation unit. You can read about validation units in the User Manual in
the section about validation scenarios.
Regards,
Sorin
Re: Problem validating XSL
Posted: Wed Sep 17, 2008 3:56 pm
by hschmitt
I am using Oxygen 9.3 Eclispe 3.3
I press the button for "Configure Validation Scenario".
In that window I select "use custom validation scenario".
Then I select "edit" for my validation scenario (created with Oxygen 9.2).
My validation scenario shows in the table the values:
URL of the file to validate: ${currentFileURL}
Validation engine: Saxon-B
Validate as you type: enabled
Extensions: 4
Then the window "Edit validation unit" shows in the drop down box for "Engine type" <Default engine> and there is no value for Saxon B.
The Button for "Extensions (4)" is grey and disabled.
So how do I get the disabled Button "Extensions (4)" enabled?
Re: Problem validating XSL
Posted: Wed Sep 17, 2008 5:05 pm
by sorin_ristache
The button Extensions is enabled only when the validator selected in the combo box Engine type allows setting extensions, for example Saxon 9. But I see that the Eclipse plugin has a bug in the list of XSLT validators displayed in the Engine type combo box: Saxon 9 B and Saxon 9 SA are not available. They are available for validation scenarios in the Oxygen standalone application but they are not available in the Eclipse plugin.
Until we fix this bug in the Eclipse plugin please copy the jar file with your extension in the lib subdirectory of the Oxygen plugin directory ([Eclipse-install-dir]/plugins/com.oxygenxml.editor_9.3.0/lib), set Saxon 9 B as default validation engine if it is not set already in Window -> Preferences -> Oxygen -> XML -> XSLT/FO/XQuery -> XSLT, restart the Eclipse platform so that the jar file is loaded in the plugin and validate your XSLT stylesheet with the toolbar button Validate Document.
Regards,
Sorin
Re: Problem validating XSL
Posted: Fri Mar 20, 2009 3:52 pm
by sorin_ristache
Hello,
walker@amigos.org wrote:when I attempt to validate an XSL stylesheet in Oxygen 9.3, I get the following message.
"SystemID: \\fs1\users$\walker\EAD\BakaYaro.xsl
Description: The transformer Saxon9B is not available anymore. Please reconfigure the transformation scenario."
hschmitt wrote:Then the window "Edit validation unit" shows in the drop down box for "Engine type" <Default engine> and there is no value for Saxon B.
The Button for "Extensions (4)" is grey and disabled.
I just wanted to let you know that we fixed the reported problems in version 10.0. You can try teh latest version from
the Download page.
Regards,
Sorin