hi,
I checked a bit about the resolver:
1) If you turn catalog-logging to 3
<parameter name="verbosity" value="3"/>
in cocoon.xconf, you can see what URL the catalog manager is trying to
load.
2) As ResolverImpl is now from the value of parameter name="catalog" an
absolute URL
is built, but the catalog manger takes this, thinks is a relative URL,
hence trying
to an URL like: file:/foo/bar/file:/x/y/z..
3) I tried a bit changing the
src.org.apache.cocoon.components.resolver.ResolverImpl avoiding
to build an absoluteURL:
.....
// Load the built-in catalog.
String catalogFile = params.getParameter("catalog",
"/resources/entities/catalog");
try {
//String catalogURL =
this.context.getResource(catalogFile).toExternalForm();
String catalogURL = catalogFile;
.....
Then building the docs works only, specifying the absolute path of the
catalog like
"/foo/bar/documentation/resources/entities",
I failed specifying file:/foo/bar/entities, in this case catalog
resolver tries to load via ftp(!?),
but perhaps it is necessary to read the API docs
of the com.sun.resolver.tools.CatalogResolver more closely.
bye bernhard
David Crossley wrote:
>Bernhard Huber wrote:
>
><snip/>
>
>>Another issue:
>>I'm not able to build the box out-of the box, as the
>>documentation/book.xml has
>>
>> <menu label="Tests">
>> <menu-item label="Catalog Test" href="catalog-test.html"/>
>> </menu>
>>
>
>The purpose of this doc is to test the Entity Resolver.
>
>>Processing catalog-test.html give me an error:
>> [java] org.xml.sax.SAXParseException: File
>>"file:/D:/projects/apache-xml/ap
>>ache-cvs-update/xml-cocoon2/build/cocoon/documentation/xdocs/ISOnum.pen"
>>not found.
>>
>
>You have encountered Bug #5060 - see Bugzilla.
>The entity resolver is failing for you. It is OK on Unix, but
>not on Windows for build docs. There have been quite a lot
>of threads on this issue - the most recent is:
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100866335220243&w=2
> [BUG] DTD validation shows bugs
>
>If anyone can help with this, then please do.
>
>>Where are the entity files expected to reside in the
>>cocoon/build/documentation hierachrachy?
>>Or do you know how to resolve the problem, without
>>uncomenting the <menu label="Tests">?
>>
>
>The entity resolver would get them for you from
>build/cocoon/documentation/resources/entities/
>--David
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
