I've tried to check the same as proposed by Thomas. If I access the server via it's host name (avoiding the ajp proxy) then I can edit the page in firedocs and the firedocs schema files appear in my /tmp/firedocs folder. All OK here!
If I use the proxy url, it gets stuck on "setting up xml editor" and no files are copied to my /tmp/firedocs folder. The last thing that seems to happen (according to my httpd log) is a get request: [01/Oct/2009:11:54:16 +0100] "GET /solutions.html?lenya.usecase=atom.entry HTTP/1.1" 200 4301 This url works fine - if I put it in the browser it does return an xml. Firedocs then tries to call this url: chrome://firedocs/content/firedocs.xul?open-uri=http%3A%2F%2Fsite.example.com%2Fsolutions.html Which fails. Interestingly, the files which get copied into the /tmp/firedocs folder are actually accessible from the proxy url, if I put the url into the browser - so the problem does not seem to be access to the schema files. Any help on how to debug this further would be a great help. Is anyone else using firedocs via an ajp proxy? If so maybe you could post your virtual host config? Regards Vik Gaurav Kalia wrote: > Hi Thomas > >> Hint: The editor keeps a local copy of schema files and stylesheets so >> you also can check what gets loaded and whatnot (see /tmp/firedocs/ or >> $home/.firedocs depending on your Firedocs version). > As Suggested by you i have checked the /tmp/firedocs/ directory, there > are two folder one with the hierarchy of my localhost and other with the > URL (cms.firedocs.com). > > I found that the files in the localhost folder are more then the one > with URL hierarchy (AJP Proxy). > > Can you please suggest how can i resolve this using the AJP Proxy. > > Thanks & Regards > Gaurav > > Thomas Comiotto wrote: >> Hi Guarav >> >>>> >>>> >>>> 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] >>>> >> >> Could be that some schema files are hiding behind the proxy. >> >> Make sure all the files referenced in the service document (including >> cross references) are in fact accesibble by the editor. >> >> Hint: The editor keeps a local copy of schema files and stylesheets so >> you also can check what gets loaded and whatnot (see /tmp/firedocs/ or >> $home/.firedocs depending on your Firedocs version). >> >> HTH >> Thomas >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
