Tom,
Do you see a problem if updateServerSession() is called much earlier
in predeploy, just after the session is created? This will allow to
initialize the loggers correctly.
Another option would be to call a subset of the methods from the
method body either relying on the state or moving them to a separate
method.
What do you think?
thanks,
-marina
-------- Original Message --------
From: mvatkina_at_dev.java.net
Subject: [Issue 998] Logging integration with GF happens too late
To: issues_at_glassfish.dev.java.net
https://glassfish.dev.java.net/issues/show_bug.cgi?id=998
User mvatkina changed the following:
What |Old value |New value
================================================================================
Summary|Logging integration with G|Logging integration with G
|F is broken |F happens too late
--------------------------------------------------------------------------------
------- Additional comments from mvatkina_at_dev.java.net Wed Aug 23 22:17:29 +0000
2006 -------
Actually, it's the first set of messages are logged at INFO level. Later on the
server session is initialized (or something else is setup), and the messages are
displayed correctly.
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: issues-help_at_glassfish.dev.java.net