zorba-coders team mailing list archive

[Chris Hillery <992304@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The following query:

module namespace foo = "http://www.zorba-xquery.com/foo";;

declare function foo:test() {
  if (fn:true())
  then 1
  else $a
};

(which is in the Zorba source as bin/test/mymod.xq) actually contacts
www.zorba-xquery.com via HTTP and attempts to download /foo.xq. This
means that the module namespace URI is undergoing URI resolution. I
cannot imagine why this would be the case, but it leads not only to
slowness but can cause the query to change behaviour depending on what
www.zorba-xquery.com chooses to return. (In the original test case, the
URL was at 28msec.com, and when 28msec.com changed from raising a 404
error to returning a 200 with an error HTML page, the query started
failing with a compilation error. Apparently Zorba was attempting to
actually compile the HTML as an XQuery.)

** Affects: zorba
     Importance: Medium
         Status: New

** Changed in: zorba
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/992304

Title:
  module declaration invokes URI resolution process

Status in Zorba - The XQuery Processor:
  New

Bug description:
  The following query:

  module namespace foo = "http://www.zorba-xquery.com/foo";;

  declare function foo:test() {
    if (fn:true())
    then 1
    else $a
  };

  (which is in the Zorba source as bin/test/mymod.xq) actually contacts
  www.zorba-xquery.com via HTTP and attempts to download /foo.xq. This
  means that the module namespace URI is undergoing URI resolution. I
  cannot imagine why this would be the case, but it leads not only to
  slowness but can cause the query to change behaviour depending on what
  www.zorba-xquery.com chooses to return. (In the original test case,
  the URL was at 28msec.com, and when 28msec.com changed from raising a
  404 error to returning a 200 with an error HTML page, the query
  started failing with a compilation error. Apparently Zorba was
  attempting to actually compile the HTML as an XQuery.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/zorba/+bug/992304/+subscriptions