Gianugo Rabellino wrote:
> David Crossley wrote:
> >Gianugo Rabellino wrote:
<snip/>
> >>Now... I tried to turn validation off in cocoon.xconf. No luck. I tried 
> >>then to resort to the entity resolver by adding the line
> >>SYSTEM "sdocbook.dtd" "sdocbook.dtd"
> >>to the end of resources/entities/catalog. No way: the little boy still 
> >>insists to have its private copy of sdocbook.dtd in the same directory.
> > 
> > That is because the alternative system identifier that you
> > have mapped here is to exactly the same URI.
> > This catalog entry should suffice:
> > SYSTEM "sdocbook.dtd" "/usr/local/sgml/docbook/simple/sdocbook.dtd"
> 
> That did the trick, and everything is working perfectly. Yet I think 
> that this part should be documented: I saw the previous SYSTEM line
> stating
> 
> SYSTEM "urn:x-arbortext:test-system-identifier"
>         "catalog-demo/testsys.xml"
> 
> so I thought that copying my "sdocbook.dtd" in resources/entities and
> declaring it as
> 
> SYSTEM "sdocbook.dtd" "sdocbook.dtd"
> 
> would have the resolver look for it in the current catalog directory, 
> which was not the case.

I think that i have sent you on a "wild-goose chase" here.
I just tried a SYSTEM entry in the "catalog" like the one that
you show. It does function correctly, and finds the resource in
the same directory as the "catalog" file.

There are two reasons that may have caused it to appear to
fail for you. You may have changed the "catalog" file after
Cocoon startup to add your new entry - however Cocoon only
reads the catalog once on startup. The other reason may be
that you did not have the resource available at the filesystem
location that you specified by the catalog entry.
--David

> It was enough to mkdir docbook, move the dtd 
> there and change the line to
> 
> SYSTEM "sdocbook.dtd" "docbook/sdocbook.dtd"
> 
> to see the problem disappear. Now I'm happy again (well... actually a 
> bit ashamed about my DTD ignorance, please bear with me ;)
> 
> Thanks for your help,
> 
> -- 
> Gianugo

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to