Page 1 of 1
XSpec & catalogs
Posted: Thu Oct 29, 2015 12:01 pm
by cmarchand
Hello,
I have defined a catalog entry in preferences : ${pdu}/catalog.xml
In my project, XSL edition and execution works perfectly.
But when I try to run XSpec in the project, the XSpec engine is not aware of the catalog. As far as XSL processor in frameworks/xspec/build.xml is saxon, it is not a problem to patch the build.xml to specify the catalog to saxon.
But :
where I can get the computed catalog from preferences, with the ${oxygen-variables} resolved ? Is there a property, a system property or anything else I could use to initialize the XSpec run ?
Thanks in advance,
Christophe
Re: XSpec & catalogs
Posted: Fri Oct 30, 2015 1:59 pm
by HomeGoods
I've a similar issue. I have
saxon.custom.options=-catalog:http://... specified in the transformation scenario and I think it is working at the first stage ("[xslt] Processing ....xspec to ....xsl") . But it doesn't seem to take effect at this stage:
Code: Select all
[xslt] Processing ...-result.xml to ...-result.html
[xslt] Loading stylesheet [Oxygen]\frameworks\xspec\src\reporter\format-xspec-report-oxygen.xsl
So if the tested xsl have <xsl:output doctype-system="http://...">, the URL isn't resolved with the catalog.
Re: XSpec & catalogs
Posted: Fri Oct 30, 2015 2:07 pm
by HomeGoods
HomeGoods wrote:I think it is working at the first stage ("[xslt] Processing ....xspec to ....xsl") .
Uh, nope. I meant the second stage ("[java] ...").
Re: XSpec & catalogs
Posted: Fri Oct 30, 2015 7:02 pm
by adrian
Hi,
cmarchand wrote:I have defined a catalog entry in preferences : ${pdu}/catalog.xml
In my project, XSL edition and execution works perfectly.
But when I try to run XSpec in the project, the XSpec engine is not aware of the catalog. As far as XSL processor in frameworks/xspec/build.xml is saxon, it is not a problem to patch the build.xml to specify the catalog to saxon.
I'm afraid that's a bug, the catalogs are not being passed to the XSpec ANT transformation. I've logged an issue for this.
cmarchand wrote:But :
where I can get the computed catalog from preferences, with the ${oxygen-variables} resolved ? Is there a property, a system property or anything else I could use to initialize the XSpec run ?
There is no property or editor variable that can be used obtain the configured XML catalogs.
One way around this would be to declare a custom editor variable for your catalog entry in Options > Preferences, Custom Editor Variables
You can then use this custom editor variable (${myCatalog}) in multiple locations (XML Catalog, scenarios, etc).
Regards,
Adrian
Re: XSpec & catalogs
Posted: Fri Apr 21, 2017 9:16 am
by Radu
Hi,
Just to update this thread, Oxygen 19.0 has two ways in which you can make XML catalogs work with XSpec:
https://www.oxygenxml.com/doc/versions/ ... sformation
Regards,
Radu