I can call each of the urls and get a page returned using the proxy
url.
You really need to follow *all* the links, including cross-references
within schema files.
The line below basically says that a schema import directive is
pointing to the void.
Error: uncaught exception: [Exception... "Component returned failure
code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]"
nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS
frame :: chrome://firedocs/content/validation/RNGSchemaParser.js ::
anonymous :: line 121" data: no]
If you want to know which file can't be found without having to do all
the handy work, add something like this to RNGSchemaParser.js (located
somewhere below your firefox profile):
113: dump(includeURI.spec)
and restart firefox from console.
Don't forget to disable xul caching and enable console dumps as
described here for instance
http://www.yulup.org/developers.html
The only strange thing I can see is calling the last url:
<edit:uri-resolver protocol="lenya-document" href="solutions.html?
lenya.usecase=atom.uuid2url&url="/>
This returns:
/staticfiredocs
Which is the publication name - but we hide this with the proxy. Could
that be an issue?
That's for resolving lenya:document links. Should be ok.
Best
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
