- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Feb 2016 10:12:59 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29462
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #1 from Michael Kay <mike@saxonica.com> ---
Noted that both these functions have error codes defined to say "No suitable
XSLT/XQuery processor available", and this can happen for a wide variety of
reasons, e.g. that some administrator has configured the system to disable
dynamic use of external XSLT/XQuery processors; these errors can be caught
using try/catch.
At this stage of the game, this seems an adequate workaround.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 16 February 2016 10:13:03 UTC