| Re: [smila-dev] logging and system.out |
|
> Of course, we could also (should?) do this by logging this instead and configuring the log to duplicate these messages to the console. i propose to do this, as it is IMO the better way. @andreas: what are are u agreeing with exactly what ju:rgen said? the above? Thomas Menzel @ brox IT-Solutions GmbH From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Andreas Weber You see not only _when_ everything is up and running under development, but also _if_ everything was started resp. not started, which is a direct indicator that something went wrong. So I agree with Jürgen here. Cheers, Von: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] Im Auftrag von Jürgen Schumacher Hi, the main reason is that when testing during development you see something to decide when you can start working: the Http server is configured to be the final service to start, so when it’s available everything should be up and running. Of course, we could also (should?) do this by logging this instead and configuring the log to duplicate these messages to the console. Cheers, Juergen. From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Menzel hi folks, recently there are quite a few statements that log to stdout instead of using a logger and also there is where it is done to both (e.g. HttpServer). Now, the latter seems to be intentional but there is no notice why this is done so. Can s.o. explain the rationale behind this? AFAIK: we had decided not to log to stdout at all. Thomas Menzel @ brox IT-Solutions GmbH Taglocity Tags: smila |