Yes I see this is what it was designed to do....I could also serialize this out by specifying a post-process function. Too much extra palava - it was only meant to be an XQuery wrapper around an already working transformation.
On Thu, Feb 11, 2021 at 2:49 PM Liam R. E. Quin <[email protected]> wrote: > On Thu, 2021-02-11 at 09:27 -0500, Ihe Onwuka wrote: > > > > However if I invoke it from XQuery with fn:transform like so > > > > xquery version "3.1"; > > fn:transform(map { 'stylesheet-node' : doc('test.xsl')})?output > > > > none of the result-documents are created. > > You need to go on my XSLT course :-) > > What happens is the content that would have been written out via > result-document ends up in the result map, with the keys being the URIs > to which they would have been written. > > So, save the result of fn:transform() and use map:keys() or map:each() > to find them and use e.g. file:write() or fn:put() or database:store- > somewhere() as appropriate. > > Liam > > > -- > Liam Quin, https://www.delightfulcomputing.com/ > Available for XML/Document/Information Architecture/XSLT/ > XSL/XQuery/Web/Text Processing/A11Y training, work & consulting. > Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.org > >
_______________________________________________ [email protected] http://x-query.com/mailman/listinfo/talk
