CLI: Cannot find catalogManager.properties

[Upayavira <uv...@upaya.co.uk>]

By default, running the CLI gives an error "Cannot find 
CatalogManager.properties". I've always just ignored it.

Someone on user list has just commented that this error can confuse (as 
to whether it is okay to ignore it), which is fair enough.

Can anyone explain how I might resolve this (or what/where 
CatalogManager.properites is?)

Regards, Upayavira

Re: [IMPIMP] care with classpath (Was: CLI: Cannot find catalogManager.properties)

[Ugo Cei <u....@cbim.it>]

David Crossley wrote:
> IMPIMP means that this is double important because
> no-one replied the first time. Please do various tests
> such as './cocoon.sh servlet' to ensure that it still
> runs on your platform.
> --David

Please consider that the "test" target might fail unless you have put 
copies of the jars contained in lib/endorsed into 
$JAVA_HOME/jre/lib/endorsed.

In other words, you might get a different XML parser and XSL-T processor 
when running "./cocoon.sh servlet" with respect to what you get when 
running "./build.sh test". This is because the first prepends 
"lib/endorsed/*.jar" to the classpath and the second does not.

At the moment, the woody block tests seem to trigger a bug in the 
version of Xalan included in Sun's JDK up to version 1.4.2 (al least on 
Linux) and thus they fail unless you do the "endorsed" trick.

	Ugo

-- 
Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
Phone: +39.0382.525100 - E-mail: u.cei@cbim.it

Re: [IMPIMP] care with classpath (Was: CLI: Cannot find catalogManager.properties)

[David Crossley <cr...@indexgeo.com.au>]

Bertrand Delacretaz wrote:
> David Crossley a écrit :
> 
> > IMPIMP means that this is double important because
> > no-one replied the first time. Please do various tests
> > such as './cocoon.sh servlet' to ensure that it still
> > runs on your platform.
> 
> Just did a clean build from current CVS on macosx/jdk 1.4.1, start with 
> "./cocoon.sh servlet".
> Tested a bunch of helloworld samples, ok.
> Petstore block sample looks ok as well.
> 
> Is that what you're looking for, or do you have more specific tests in 
> mind?

Thanks. Nothing specific in mind, merely that i was horrified
to be adding something to the classpath of the planet's
infrastructure, aka cocoon.

I would like someone to cast their eye over those code changes
to ensure nothing drastic.

--David

Re: [IMPIMP] care with classpath (Was: CLI: Cannot find catalogManager.properties)

[Bertrand Delacretaz <bd...@apache.org>]

Le Jeudi, 30 oct 2003, à 05:42 Europe/Zurich, David Crossley a écrit :

> IMPIMP means that this is double important because
> no-one replied the first time. Please do various tests
> such as './cocoon.sh servlet' to ensure that it still
> runs on your platform.

Just did a clean build from current CVS on macosx/jdk 1.4.1, start with 
"./cocoon.sh servlet".
Tested a bunch of helloworld samples, ok.
Petstore block sample looks ok as well.

Is that what you're looking for, or do you have more specific tests in 
mind?

-Bertrand

[IMPIMP] care with classpath (Was: CLI: Cannot find catalogManager.properties)

[David Crossley <cr...@indexgeo.com.au>]

IMPIMP means that this is double important because
no-one replied the first time. Please do various tests
such as './cocoon.sh servlet' to ensure that it still
runs on your platform.
--David

On 2003-10-19 David Crossley wrote:
> Important: I presume that everyone gets the jitters when messing
> with the classpath. So would someone else please verify that
> there are no side-effects. I also tested the Woody CarSelector.
> --David
> 
> David Crossley wrote:
> > David Crossley wrote:
> > > Upayavira wrote:
> > > > By default, running the CLI gives an error "Cannot find 
> > > > CatalogManager.properties". I've always just ignored it.
> > 
> > Your recent mods to cocoon.sh|bat did not fix it. The file needs
> > to be available on the *classpath*. This fix did the trick for me:
> > 111c111
> > <LOADER_LIB="$COCOON_HOME/tools/loader"
> > ---
> > >LOADER_LIB="$COCOON_HOME/tools/loader:$COCOON_WEBAPP_HOME/WEB-INF/classes"
> > 
> > I committed that fix, so please test on Win.
> > 
> > --David

[IMP] care with classpath (Was: CLI: Cannot find catalogManager.properties)

[David Crossley <cr...@indexgeo.com.au>]

Important: I presume that everyone gets the jitters when messing
with the classpath. So would someone else please verify that
there are no side-effects. I also tested the Woody CarSelector.
--David

David Crossley wrote:
> David Crossley wrote:
> > Upayavira wrote:
> > > By default, running the CLI gives an error "Cannot find 
> > > CatalogManager.properties". I've always just ignored it.
> 
> Your recent mods to cocoon.sh|bat did not fix it. The file needs
> to be available on the *classpath*. This fix did the trick for me:
> 111c111
> <LOADER_LIB="$COCOON_HOME/tools/loader"
> ---
> >LOADER_LIB="$COCOON_HOME/tools/loader:$COCOON_WEBAPP_HOME/WEB-INF/classes"
> 
> I committed that fix, so please test on Win.
> 
> --David

Re: CLI: Cannot find catalogManager.properties

[Upayavira <uv...@upaya.co.uk>]

David Crossley wrote:

>David Crossley wrote:
>  
>
>>Upayavira wrote:
>>    
>>
>>>By default, running the CLI gives an error "Cannot find 
>>>CatalogManager.properties". I've always just ignored it.
>>>
>>>Someone on user list has just commented that this error can confuse (as 
>>>to whether it is okay to ignore it), which is fair enough.
>>>
>>>Can anyone explain how I might resolve this (or what/where 
>>>CatalogManager.properites is?)
>>>      
>>>
>>It is part of the entity-resolver and needs to be available
>>on the classpath when the resolver starts, which i guess is on
>>the first parse of the first xml file.
>>
>>Cocoon usually finds it in WEB-INF/classes/
>>    
>>
>
>Your recent mods to cocoon.sh|bat did not fix it. The file needs
>to be available on the *classpath*. This fix did the trick for me:
>111c111
><LOADER_LIB="$COCOON_HOME/tools/loader"
>---
>  
>
>>LOADER_LIB="$COCOON_HOME/tools/loader:$COCOON_WEBAPP_HOME/WEB-INF/classes"
>>    
>>
>
>I committed that fix, so please test on Win.
>  
>
Whilst my fix worked on Windows, I've tested yours on the CLI, and the 
servlet and it worked too.

Regards, Upayavira

Re: CLI: Cannot find catalogManager.properties

[David Crossley <cr...@indexgeo.com.au>]

David Crossley wrote:
> Upayavira wrote:
> > By default, running the CLI gives an error "Cannot find 
> > CatalogManager.properties". I've always just ignored it.
> >
> > Someone on user list has just commented that this error can confuse (as 
> > to whether it is okay to ignore it), which is fair enough.
> > 
> > Can anyone explain how I might resolve this (or what/where 
> > CatalogManager.properites is?)
> 
> It is part of the entity-resolver and needs to be available
> on the classpath when the resolver starts, which i guess is on
> the first parse of the first xml file.
> 
> Cocoon usually finds it in WEB-INF/classes/

Your recent mods to cocoon.sh|bat did not fix it. The file needs
to be available on the *classpath*. This fix did the trick for me:
111c111
<LOADER_LIB="$COCOON_HOME/tools/loader"
---
>LOADER_LIB="$COCOON_HOME/tools/loader:$COCOON_WEBAPP_HOME/WEB-INF/classes"

I committed that fix, so please test on Win.

--David

Re: CLI: Cannot find catalogManager.properties

[David Crossley <cr...@indexgeo.com.au>]

Upayavira wrote:
> By default, running the CLI gives an error "Cannot find 
> CatalogManager.properties". I've always just ignored it.
>
> Someone on user list has just commented that this error can confuse (as 
> to whether it is okay to ignore it), which is fair enough.
> 
> Can anyone explain how I might resolve this (or what/where 
> CatalogManager.properites is?)

It is part of the entity-resolver and needs to be available
on the classpath when the resolver starts, which i guess is on
the first parse of the first xml file.

Cocoon usually finds it in WEB-INF/classes/

--David