Re: Firedocs Editor Problem

Hi Sac


>
> 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.

That should be ok. The default port gets substituted by 80 when  
storing the local copy of the Uri.

However you can put some alerts to URICache.js:171 and see what port  
information you get for the remote schema files (not the local copy).

Make sure to clear the cached files first (remove the whole local  
schema folder structure).



>
>
> 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.


This looks like the interesting part. Is lenya.rng (the remote file)  
actually accessible from the server?

I am not sure if this is a Lenya or a Firedocs issue, so let's move  
this discussion to a private channel and post a summary to the list  
when we're finished.

Cheers
Thomas