Re: DOCBOOK-APPS: DocBook and Cocoon

[Sven Kitschke <kicke@web.de>]

Hi,

Michael Cortez wrote:
[snip]
 > Lots of:
 > ====================================
 > No localization exists for "en" or "". Using default "en".
 > No "en" localization of "TableofContents" exists.
 > No localization exists for "en" or "". Using default "en".
 > No "en" localization exists.
 > ====================================
 >
I assume you are using Cocoon-2.0.2. I ran into the same problems.
I have also tried saxon-6.5.2.
I assume the cause for the localization error are problems with the 
entity resolution.

In the <tomcat-dir>\webapps\cocoon\WEB-INF\logs\core.log you
can find: "java.net.MalformedURLException: no protocol: af.xml"
(adding "file:" doesn't fix the problem)

af.xml (and others) are external entities declared in l10n.xml
which is loaded through the document-function in l10n.xsl ...
It seems that aelfred (the parser that comes with saxon) cannot
resolve the file location of these entities.

Today i have found three workarounds:
1) Use absolute file names :-( in l10n.xml like:
<!ENTITY af SYSTEM "file:///e:/the-path-to-dbxsl/common/af.xml">

2) Replace xalan.jar (2.3.1), xml-apis.jar and xerces.jar (2.0.0)
with that from the Cocoon-2.0.1 distribution in the web-inf/lib
directory.
Hm.

3) Patch saxon.jar:
Change the content of
META-INF/services/javax.xml.parsers.SAXParserFactory from
com.icl.saxon.aelfred.SAXParserFactoryImpl to
org.apache.xerces.jaxp.SAXParserFactoryImpl. That tells
Saxon to use xerces instead of aelfred as parser.
Also Hm. But it works for now.

I know that's the wrong list, but: has anyone an idea
where the bug resides? Is it a configuration problem
or bug in cocoon or a bug in saxon/aelfred?
Is there an easier way to configure cocoon to use a
saxon/xerces configuration?


-- 
Sven Kitschke
mailto: kicke@web.de