Hi Thomas Can you let me know from where the javascripts get the path? Right now the heirarchy which firedocs is creating in the /tmp directory is different than the heirarchy it javascript alert shows for "includeURI.spec" in RNGSchemaParser.
The heirarchy made by firedocs in /tmp is having directory "80"(for http port) in it but javascript alert shows path without "80" directory in it. And also the lenya.rng produced is an lenya error file with error-404. There is no dublincore produced. Regards Sac On Thu, Oct 1, 2009 at 3:39 PM, Thomas Comiotto <[email protected]>wrote: > >> 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] > > -- Regards Sachin Sharma
