Re: Firedocs Editor Problem

Hi All

I looked into the issue and find out some thing interesting:

The first thing I noticed is the dublincore directory with the
dublincore.rng is missing in case I use the direct url. I dont know why but
all other files are being copied but not this one.

Second: If I put /pubname/area in front of the url all works fine.

My URLs and directory structure in the tmp are :

*Case 1: http://cms.example.co.uk/test.html*
/tmp/firedocs/schema/uk/co/example/cms/80/lenya and
/tmp/firedocs/schema/uk/co/example/cms/80/modules

In this case firedocs says file not found.

*Case 2: http://cms.example.co.uk/lenya/mypub/authoring/test.html*
/tmp/firedocs/schema/uk/co/example/cms/80/mycontext/lenya and
/tmp/firedocs/schema/uk/co/example/cms/80/mycontext/mypub/modules

In this case firedocs works fine.

Obviously two different file structures here. Any suggestions.

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