Indeed. It's a bug, but was recently fixed in 6.0-3. -Will
On 9/25/13 3:54 AM, "Geert Josten" <[email protected]> wrote: >Sounds like a good candidate for support at marklogic.. > >;-) > >> -----Oorspronkelijk bericht----- >> Van: [email protected] [mailto:general- >> [email protected]] Namens Will Thompson >> Verzonden: dinsdag 24 september 2013 3:50 >> Aan: MarkLogic Discussion >> Onderwerp: [MarkLogic Dev General] Resolving relative paths in XSLT with >> xdmp:import-module >> >> An XSLT is created dynamically in ModuleRoot/X/Y/Z/A.xqy and executed >> using xdmp:xslt-eval(). A.xqy imports B.xqm (using xdmp:import-module) >> and >> C.xsl, both using relative paths. B.xqm resolves to ModuleRoot/B.xqm, >but >> C.xsl resolves ModuleRoot/X/Y/Z/C.xsl. If an XSLT file is created and >> executed using xdmp:xslt-invoke(), B.xqm resolves to >> ModuleRoot/X/Y/Z/B.xqm. >> >> I suspect this is a bug, since I would expect paths to resolve relative >to >> the path executing the XSLT, whether the XSLT is executed with >> xslt-invoke() or xslt-eval(). But I thought there was a chance I don't >> understand something about xdmp:import-module... >> >> -Will >> >> _______________________________________________ >> General mailing list >> [email protected] >> http://developer.marklogic.com/mailman/listinfo/general >_______________________________________________ >General mailing list >[email protected] >http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
