Current design can never deal with relative xincludes

[GoogleCodeExporter]

Because we do:

DOMDocument::loadXML(), having implemented out Very Own content
negotiation, we can't rely on DOMDocument::xinclude() working properly.

If you do a loadXML, it's not going to set the baseURI.

If you do an xinclude, it's going to try and do its own get-me-this-file stuff.

Solutions:
 * Hack until it goes away; by fetching all files that would be xincluded
and writing them to a tempdir. Swith chdir() and then revert back, so that
DOMDocument loads it locally.
 * Restructure internals to pass around a URL or getDOMInstance($url) method?

Original issue reported on code.google.com by daniel.o...@gmail.com on 2 Mar 2008 at 2:07

[GoogleCodeExporter]

I'm moving this to wontfix, as this passes an alternative test

Original comment by daniel.o...@gmail.com on 20 Mar 2008 at 2:59

• Changed state: WontFix