Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Crossley <crossley@indexgeo.com.au>
Reply-To: crossley@indexgeo.com.au
To: cocoon-dev@xml.apache.org
Subject: entity catalogs - success/failure reports please
Date: Sat, 1 Sep 2001 01:34:48 +1000
MIME-Version: 1.0
Message-Id: <01090101344802.03795@localhost.localdomain>
Content-Transfer-Encoding: 8bit

We need to confirm that the new entity resolution capability performs
correctly on all major platforms. Would you please send a brief
yes or no, together with your platform details, directly to me and i will
collate the replies.

With the lastest 2.1-dev HEAD branch, the CatalogManager.properties
is automatically copied to your classpath via WEB-INF/classes/
by the build process, and the path to the default catalog is
automatically configured.

Try the Welcome page demo to start Cocoon. If you see the STDOUT
message "Cannot find CatalogManager.properties" then there is a
problem with finding the properties file on your classpath. Otherwise,
if you have set verbosity>1 then you will see catalog loading status
messages going to STDOUT.

Then try the link to the Entity Catalogs demo. Please tell us how you
go. You will either successfully get the rendered demo page or you
will get an "Error creating the resource" could not find ISOnum.pen

Here are the reports that we have so far ...

-------------------------------
Success
------
* Linux Red Hat 7.1, java.vm.version=Blackdown-1.3.1-FCS, Tomcat 3.2.2
* Win2K, Tomcat 3.3

-------------------------------
Failure
-----
* Windows 2000 Professional, Tomcat 3.2.1
 - pathname problems with interpreting directory separator

-------------------------------
thanks, David Crossley

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