Return-Path: 
 <cocoon-dev-return-20400-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 47629 invoked by uid 500); 28 Dec 2001 00:04:31 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 47618 invoked from network); 28 Dec 2001 00:04:30 -0000
Message-ID: <3C2BB656.6070207@a1.net>
Date: Fri, 28 Dec 2001 01:01:26 +0100
From: "Bernhard Huber" <berni_huber@a1.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: build docs fails on Windows -[Was] VOTE: Restructuring FAQ file
References: <3C27BAE6.6060708@a1.net> <01122518523900.00848@igacer>
 <3C283C44.4000202@a1.net> <01122612033901.00848@igacer>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

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: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org