>>> [ disable / dont show Boot Logger messages ]
>>
>>BTW: why don't you like this message?
>
> Automated tests are supposed to be silent when successful. This
> prevents that. When I run 300 unit-tests that all pass, I expect to see
> no output on the screen. When I do, I assume something is wrong.
>
> Furthermore, any many imaginable environments, stdout is not what you
> think it is.
I've got a similar itch: We are using log4j in our product and of course
for OJB as well and this works like a charm. As far as I know the
BootLogger doesn't use log4j in this set-up for two reasons:
1.) As no configuration is loaded, it doesn't even know that I want to use
Log4J for logging
2.) It thinks that it has to configure log4j to do successfull logging
the first assumption is true, the second isn't ('cause we do log4j
configuration before we even start using ojb).
I think it would be nice to be able to tell OJB which logger to use,
before configuration starts.
Any comments?
regards
Joachim Sauer
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
