cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Lavoie <philippe.lav...@cactus.ca>
Subject RE: odd behavior
Date Mon, 17 Jan 2000 14:34:23 GMT
I'm in the 'fail fast' school of thought so I'd say stick with what you have
now.

Since Cocoon, isn't meant to be configured by non-educated users. It's
just part of the education to know that what's in your property file should
be good and valid information.

Phil

> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org]
> Sent: Sunday, January 16, 2000 5:40 PM
> To: cocoon-dev@xml.apache.org
> Subject: Re: odd behavior
> 
> 
> Michael Engelhart wrote:
> > 
> > I just noticed that if you have a Producer listed in your 
> cocoon.properties
> > file and the class associated with it is not in your 
> classpath anymore,
> > Cocoon stops the initialization process.  Shouldn' the 
> behavior at least
> > display a message to stdout or better yet display a message and then
> > continue on with the initialization process so that Cocoon 
> at least works
> > for the remaining Producers/Processors?
> 
> I'm kind of neutral to this. What do other think?
> 
> Stefano.
> 
> 

Mime
View raw message