zorba-coders team mailing list archive

[Chris Hillery <948879@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The zorbacmd command-line arguments --uri-path, --lib-path, and
--module-path modify the StaticContext that runs the query. However, if
this query invokes the fetch module, the invocation of fetch:content()
is in a separate StaticContext that does not inherit those paths. The
upshot is that you can't fetch content from any custom paths, only the
built-in Zorba paths.

** Affects: zorba
     Importance: High
     Assignee: Matthias Brantner (matthias-brantner)
         Status: New

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

** Changed in: zorba
     Assignee: (unassigned) => Matthias Brantner (matthias-brantner)

** Description changed:

  The zorbacmd command-line arguments --uri-path, --lib-path, and
  --module-path modify the StaticContext that runs the query. However, if
  this query invokes the fetch module, the invocation of fetch:content()
  is in a separate StaticContext that does not inherit those paths. The
  upshot is that you can't fetch content from any custom paths, only the
- build-in Zorba paths.
+ built-in Zorba paths.

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

Title:
  --uri-path doesn't work with fetch:content()

Status in Zorba - The XQuery Processor:
  New

Bug description:
  The zorbacmd command-line arguments --uri-path, --lib-path, and
  --module-path modify the StaticContext that runs the query. However,
  if this query invokes the fetch module, the invocation of
  fetch:content() is in a separate StaticContext that does not inherit
  those paths. The upshot is that you can't fetch content from any
  custom paths, only the built-in Zorba paths.

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