I generally agree although I think it may be useful in many cases to log the exception (for developers) at a higher (usually off) log level.
On Jun 1, 2008, at 4:51 PM, Steven Harris wrote: > One area where I think their is a little bit of inconsistency in the > Terracotta product is when to use clear error messages > and when stack traces are ok. > > I've of the opinion that any known condition should be a clear error > message with no stack trace. The only times a stack trace should > ever be thrown are when: > a) A condition occurs where it would be useful for debugging > b) Something occurs that is completely not expected (assertion error, > npe, etc). > > In most cases in Terracotta we do a reasonable job of this but we > still have a few niggling areas that throw stack traces that > shouldn't. > > I think we should at some point do a reasonably quick audit of the > code and clean up the rest of them. > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
