Hi Vik When I append 80 to the url it automatically converts it into 'without 80' url by removing ":80" from the url.
Regards Sac On Sun, Oct 4, 2009 at 9:33 AM, Vik Tara <[email protected]> wrote: > And when I put the path into my browser it says no such file. But when I > insert 80 to the path it shows the proper file. So I am sure that the > problem is due to that '80' figure. > > > So if you append :80 to your proxy url - does firedocs then work? > > Vik > > > > On 04/10/09 01:33, sac sha wrote: > > Hi All > > I have put some alerts to the javascript(includeURI.spec) and find out that > the path to the file is coming incorrect. The path to the rngs stored in my > system is having a directory for port 80 with the name '80', but the > javascript alert is giving me the path omitting this directory. > > And when I put the path into my browser it says no such file. But when I > insert 80 to the path it shows the proper file. So I am sure that the > problem is due to that '80' figure. > > file:///tmp/firedocs/schema/uk/co/example/cms/lenya/schemas/lenya.rng -> > Gives error (file not found) > file:///tmp/firedocs/schema/uk/co/example/cms/80/lenya/schemas/lenya.rng-> > (shows proper file) > > Not sure but can this be because of url proxying? > > Adding to this... > the lenya.rng on the wrong path(as above) is an xml file having wrong data > i.e page not found data of lenya. And also no dublincore directory and > dublincore.rng present :-) > > 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 > > > -- Regards Sachin Sharma
