Hi Mark,
Have you tried using a URI?
file:///somewhere/somethingorother.foo
I'm not sure how the code reacts if parameters are not URIs.
Dave
"Mark Weaver"
<[EMAIL PROTECTED] To: "Xalan-Dev"
<[EMAIL PROTECTED]>
> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: XalanC: bug in relative URI
resolving or my brain?
02/02/2003 10:13
PM
Please respond
to xalan-dev
Xalan-C 1.4 on w2k.
At some point, I'm calling
XPathExecutionContext::parseXML("/somewhere/somethingorother.foo",
"http://localhost/blah/blah/blah.foo"). The URI is then resolved to
http://localhost/blah/blah/somewhere/somethingorother.foo. This seems
wrong
to me - RFC2396 has "5) If the path component begins with a slash
character
("/"), then the reference is an absolute-path and we skip to step 7." in
"5.2. Resolving Relative References to Absolute Form". The same happens
for
other such includes (e.g. in stylesheets).
Sorry if this has come up before. I've had a quick dig through bugzilla,
and can't find anything. Either way, let me know and i'll fix/tell my
users
to go away as appropriate...
Thanks,
Mark
Re: XalanC: bug in relative URI resolving or my brain?
David N Bertoni/Cambridge/IBM Mon, 03 Feb 2003 08:52:46 -0800
- XalanC: bug in relative URI resolving or my ... Mark Weaver
- RE: XalanC: bug in relative URI resolvi... David N Bertoni/Cambridge/IBM
- RE: XalanC: bug in relative URI res... Mark Weaver
- RE: XalanC: bug in relative URI... David N Bertoni/Cambridge/IBM
- RE: XalanC: bug in relative... Mark Weaver
- RE: XalanC: bug in relative URI resolvi... Mark Weaver
