Failure setting relative base-uri when no absolute base known
Bug #1169191 reported by
Sorin Marian Nasoi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zorba |
Fix Released
|
Medium
|
Chris Hillery |
Bug Description
Test cases xqhof16 to xqhof18 in misc-HigherOrde
</tmp/query_
Related branches
lp:~zorba-coders/zorba/bug-1169191
- Markos Zaharioudakis: Approve
- Chris Hillery: Approve
-
Diff: 32 lines (+6/-5)2 files modifiedsrc/context/static_context.cpp (+6/-4)
test/fots/CMakeLists.txt (+0/-1)
Changed in zorba: | |
status: | New → Fix Committed |
Changed in zorba: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The problem turns out to be in static_ context: set_base_ uri(). In this case, the entity-retrieval URI for the module itself is just "lib", since (due to the XQXQ URL resolver) Zorba has no way of knowing the actual URI used to load the module. This entity-retrieval URI is used as the absolute base URI to resolve the declared base URI of "lib" against, but since the entity-retrieval URI isn't itself absolute, URI::resolve_uri() dies with the error.