Rick Tessner wrote:
> On Sat, 2002-08-10 at 01:24, Ross Gardler wrote:
>
>
>>Yes, below are the log snippets that I get when I make the DOCTYPE point
>>at the documentv11.dtd via the full path. Note the file it can't find,
>>ISOlat1.pen, is to be found in
>>/home/rgardler/projects/research/saafe/build/work/resources/schema/entity,
>>which is correctly defined in the catalog).
>>
>>If I change the doctype to not have the full path to the dtd I get the
>>same error but the file it can't find is
>>/home/rgardler/projects/research/saafe/build/work/content/xdocs/document-v11.dtd
>>(this is the directory in which the documents to be aggregated are found
>>are found)
>
> When you say you change the DOCTYPE to point at "document-v11.dtd" with
> fullpath or not, I take it you mean changing it in one of your
> documents?
Yes.
> If that's the case, then I'd guess that the catalog stuff is either not
> being used or is not correctly configured. If the catalog stuff was
> being used, Cocoon would be finding the PUBLIC identifier
> ("-//APACHE/DTD Documentation V1.1//EN") and using the information in
> the catalog to locate the document-v11.dtd and friends. The SYSTEM
> identifier doesn't even have to physically exist as a file(if the PUBLIC
> identifier is being used correctly).
I think the catalog stuff is being used by Cocoon for the normal
translations, but not for the <apply-templates
select="document(@href)"/> stuff.
The lines you refer to below do appear in my core.log file, a few of the
relevant lines are copied below. Perhaps this is actually a bug, should
I put it on bugzilla and see what the developers think? With your help
we seem to have created enough info for the problem to be tracked down.
core.log
--------
<snip/>
DEBUG (2002-08-11) 16:24.26:248 [core.resolver] (Unknown-URI)
Unknown-thread/ResolverImpl: Resolved catalog entity: -//APACHE//DTD
Documentation V1.1//EN
file:/home/rgardler/projects/research/saafe/build/work/resources/schema/dtd/document-v11.dtd
<snip/>
DEBUG (2002-08-11) 16:24.26:248 [core.resolver] (Unknown-URI)
Unknown-thread/ResolverImpl: Resolved catalog entity: -//APACHE//DTD
Documentation V1.1//EN
file:/home/rgardler/projects/research/saafe/build/work/resources/schema/dtd/document-v11.dtd
DEBUG (2002-08-11) 16:24.26:248 [core.resolver] (Unknown-URI)
Unknown-thread/ResolverImpl: Resolved catalog entity: -//APACHE//DTD
Documentation V1.1//EN
file:/home/rgardler/projects/research/saafe/build/work/resources/schema/dtd/document-v11.dtd
<snip/>
>
> Could you check a log file called core.log (should be under
> WEB-INF/logs/) and look for "Resolved catalog entity". You should find
> entries that look like this:
>
> DEBUG (2002-08-11) 07:47.49:515 [core.resolver]
> (/Forrest/index.html) tcpConnection-6802-1/ResolverImpl: Resolved
> catalog entity: -//APACHE//DTD Cocoon Documentation Book V1.0//EN
> file:/usr/local/resin/webapps/Forrest/resources/schema/dtd/book-cocoon-v10.dtd
> but with "Book V1.1" and resolving to file:
> "<something>/resources/schema/dtd/document-v11.dtd".
>
> You should also be seeing entries for all the other entities that are
> being referenced by document-v11.dtd (like ISOlat.pen etc).
>
> If you're not seeing these, shutdown your cocoon instance, delete the
> WEB-INF/tmp/cocoon-files directory and restart. (There may be a caching
> issue of some kind ...)
>
> Hope this helps,
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
