| Phocus |
| Member |
| Phocus |
| MU |
|
| compilers, solid state physics, paragliding |
| Male |
|
| Tuesday, October 29, 2002 |
| Monday, November 27, 2017 7:42:12 AM |
6
[0.03% of all post / 0.00 posts per day] |
|
Hi,
The file is invalid because the 'console' variable in the msxsl script is not declared.
Not sure what you want to achieve with your javascript code. As it is it will be compiled and made available during the xslt transformation.
If you want the javascript to be included in the generated html file then you must create a <script> element. If you want to wrap with //<![CDATA[ ... //]]> you can add a special character with entity ref before and after the script code and use character maps to remap to //<![CDATA[ and //]]>.
Also note that the exclude-result-prefixes applies to the descendant literal elements - so putting it on the xsl:output element will not have the desired effect - better would be to have it on the xsl:stylesheet.
Hope this helps.
+
|
Hi,
without additional information it's not possible to identify where&when the problem occurs. You should attach your design -reduced to minimal- that demonstrates the problem. Also don't forget to include the schema and working xml files as well.
Or even better: contact Altova support with your files and used configuration (fop version etc)
Cheers
+
|
Hi,
from the stack trace this error seems to be unrelated to StyleVision and you would probably want to look at the content returned by the request.getParameter("template") call on line 21
+
|
hi,
the msxsl:script falls in the category of xslt extension elements, initially implemented by MSXML and is supported in the newer versions of the built-in XSLT engine used in Altova XMLSpy.
Tried your sample in XMLSpy2009 and worked fine with the built-in engine.
Best regards,
Botond
+
|
hi tshmi,
with the files under c:/coding/collections/ the call collection('c:/coding/collections/*.xml') should return the document nodes for all files in that folder with xml extension.
I use the following code to retrieve information from several *.xsl files. Works perfectly with both XMLSpy and AltovaXML. I use the latest version: 2008 rel. 2 sp2.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" >
<xsl:output indent="yes"/>
<xsl:template match="/">
<out>
<xsl:for-each select='collection( "C:\Program Files\Altova\XMLSpy2008\sps\Template\xmlspec\*.xsl" )/*/xsl:template/@match'>
<temp match="{.}"/>
</xsl:for-each>
</out>
</xsl:template>
</xsl:stylesheet>
Best regards,
Botond
+
|
Astir,
In order to enforce the output to a zip file one has to specify the zip protocol:
a) either on the href attribute (output uri) of every xsl:result-document
b) or if the result-documents specify relative output uris -as I assume is in this case-, then for the main output. The folder extracted from the main output is used as the base output uri to resolve the relative output uris.
ex:
xslt2.Execute(CurrentDirectory+"/orgchart.docx|zip/main.out");
or if the main result document is empty:
xslt2.Execute(CurrentDirectory+"/orgchart.docx|zip/");
For regular zip archives this would be:
xslt2.Execute(CurrentDirectory+"/results.zip|zip/result0001.xml");
When using from command line, since the | ( pipe ) character is interpreted in the windows cmd system, you have to put quotes around the main output uri.
AltovaXML -in input.xml -xslt2 transform.xslt -out "results.zip|zip\result003.xml"
Cheers,
Botond
+
|
|
