Thank Vincent, But it the input of the xslt I want to control. I'm using BaseX with the CHOP false because I use text documentation and space is important at the end or the begining of an element, and when I try to use xslt (with baseX 7) it serialize with indent true the input of my xslt, so I lost the space. Marc Le 03/08/2015 23:07, Lizzi, Vincent a écrit :
Thanks, Max and Andy. The XQuery 3.1 transform function looks promising.Marc, For controlling the serialization of XSLT output, you can specify serialization for the XSLT within the XSLT itself using xsl:output, run the XSLT using the xslt:transform-text, and then write the output to a file. file:write-text('file.txt', xslt:transform-text($doc, $xslt)) I'm not sure if this will do what you need, but so far it has been working for me. Vincent -----Original Message----- From: basex-talk-boun...@mailman.uni-konstanz.de [mailto:basex-talk-boun...@mailman.uni-konstanz.de] On Behalf Of Marc Sent: Monday, August 03, 2015 4:53 PM Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Destination of result-document from XSLT module Hi, I have an other problem is to control the serialization of the node passed to the transform function. I don't see how to control it. Marc Le 03/08/2015 22:32, Andy Bunce a écrit : > Hi Max, > This sounds like a good thing. > Another solution to the result-document issue might be to implement > the XQuery 3.1 transform function [1] > > /Andy > [1] http://www.w3.org/TR/xpath-functions-31/#func-transform > > On 3 August 2015 at 20:54, Max Goltzsche <max.goltzs...@algorythm.de > <mailto:max.goltzs...@algorythm.de>> wrote: > > Hello Vincent, > > besides an URI resolver I also want to set XSLT 2.0's output > destination in BaseX. > Currently as you can see in BaseX' xslt:transform and > xslt:transform-text implementation in > https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/basex/query/func/xslt/XsltTransform.java > there is neither an URIResolver or OutputURIResolver set on the > Transformer nor a destination systemId set on its StreamResult. Thus > Saxon resolves output paths relative to your Java process' working > directory (in fact all relative XSL include, import, document and > collection paths in the XSLT passed to the transform method). > Unfortunately to change this behaviour the XsltTransform class must > be enhanced. > If you need a quicker* solution for your problem you may have to > build your own BaseX transform Java Module based on the > XsltTransform class setting at least the StreamResult's systemId I > think. > I will be also working on this the next evenings. > > best regards, > Max > > > On 03.08.2015 20:54, Lizzi, Vincent wrote: >> >> I’m trying to use the XSLT Module in BaseX 8.2.3 with Saxon 9.6 to >> run an XSLT that produces several output documents using >> xsl:result-document. I’m having trouble setting the location of >> the output documents. I want to have xsl:result-document create >> the output documents in a temporary folder because the documents >> need to be zipped together. ____ >> >> __ __ >> >> According to Saxon’s documentation, the a relative path in the >> href attribute of xsl:result-document will be resolved using >> either the path of the Destination, or the current directory. The >> XSLT Module does not appear have a way to provide a path for a >> destination document. What I’m seeing is that the result >> documents are created in BaseX’s home directory. The XSLT works as >> expected when run using Saxon from the command line, where it’s >> possible to set a destination path.____ >> >> __ __ >> >> Is there a way to specify a Base Output URI to the XSLT Module? >> Or, would it be possible to specify a file URI output location to >> a method like xslt:transform?____ >> >> __ __ >> >> One possible workaround is to provide an absolute path as a >> parameter to the XSLT, and use that parameter in the >> xsl:result-document href location. ____ >> >> __ __ >> >> Here is a self-contained example code:____ >> >> __ __ >> >> __ __ >> >> declare function local:example($in, $xsl, $zipPath) {____ >> >> let $tempDir := file:create-temp-dir('test', 'example')____ >> >> let $x := xslt:transform-text($in, $xsl)____ >> >> return ____ >> >> let $zip := archive:create-from($tempDir)____ >> >> return (____ >> >> file:write-binary($zipPath, $zip)____ >> >> (: , file:delete($tempDir, true()) :)____ >> >> )____ >> >> };____ >> >> __ __ >> >> __ __ >> >> let $xsl := <xsl:stylesheet >> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; >> <http://www.w3.org/1999/XSL/Transform> >> xmlns:xs="http://www.w3.org/2001/XMLSchema"; >> <http://www.w3.org/2001/XMLSchema> version="2.0">____ >> >> <xsl:template match="/">____ >> >> <xsl:result-document href="doc1.xml">____ >> >> <test>this is a test 1 >> <xsl:apply-templates/></test>____ >> >> </xsl:result-document>____ >> >> <xsl:result-document href="doc2.xml">____ >> >> <test>this is a test 2 >> <xsl:apply-templates/></test>____ >> >> </xsl:result-document>____ >> >> </xsl:template>____ >> >> </xsl:stylesheet>____ >> >> __ __ >> >> let $doc := <test>this is input</test>____ >> >> __ __ >> >> let $zipPath := 'report.zip'____ >> >> __ __ >> >> return local:example($doc, $xsl, $zipPath)____ >> >> __ __ >> >> The expected output is a zip file report.zip that contains >> doc1.xml and doc2.xml. ____ >> >> __ __ >> >> However, what I’m seeing is that report.zip is created as an empty >> zip file and doc1.xml and doc2.xml are placed in BaseX’s home >> directory.____ >> >> __ __ >> >> Thanks,____ >> >> Vincent____ >> > >
