Hi Scott,
Jerome and I were just talking about this general issue the other day.
That is the usage of anonymous loggers in v3. The conclusion was that
we'd go through the code and figure out which anonymous loggers can be
changed to use a GF logger. The logging service is one of the first
services to start up but it is not the first. I believe one issue is
that we can have messages that need to be logged before the logging
service is started.
I'll look into changing the loggers that are used for std out/err to not
be anonymous loggers. Most likely will not happen for v3 unless you can
convince Jerome that it should.
Carla
Scott Oaks wrote:
> In v3, the standard out/err loggers now appear to be anonymous loggers,
> which means that we cannot control their output directly. The
> logging.properties can have something like
> .level=OFF
> so that the anonymous loggers inherit that default setting, but that
> affects other loggers not defined in the logging.properties file.
>
> Is this really the intended behavior, or am I missing something? We
> often see developers write noisy applications that use
> System.out.println or printStackTrace() and need turn off those messages
> during production. Yes, they should use a logger, but they don't always
> do so, and previously we've always just adjusted the system.out/err
> logging properties.
>
> -Scott
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>