|
[XQuery Talk Mailing List Archive Home] [By Date] [By Thread] [By Subject] [By Author] [Recent Entries] [Reply To This Message] multiple xquery implementations running side by sideWolfgang Meier wolfgang at exist-db.orgMon May 21 00:13:19 PDT 2007
Hi, > I was wondering if anyone saw any benefits to running xquery > implementations connected to each other, I am specifically thinking of > if I use Saxon as the transformer for Exist, then i end up with a > second Xquery implementation. Any ideas on how this can be made use > of? Do you have any concrete problems with this setup? eXist can use saxon (or other implementations) as an XSLT engine, e.g. if you call an XSLT stylesheet via the transform() extension function from XQuery. The main purpose of this function is to easily post-process XML fragments produced by your XQuery. You could probably do the same job in XQuery code, but XSLT is sometimes just more convenient. Forwarding to saxon certainly implies a small overhead, though it is usually ignorable if you are just post-processing smaller chunks of XML (and that's what the function is intended for). Wolfgang
|
Purchase Stylus Studio Online Today!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|






