You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What our config framework provides is a simple event system. When logging is done you can drain the queue of events usually replaying them to logging our System.err.
The reason for doing this is because sometimes we want the configuration to load completely BEFORE any logging is used. This allows the configuration to put things into System Properties which is used to configure the actual logging.
The text was updated successfully, but these errors were encountered:
so the first thing that comes to mind is to take the logs we output and keep them in a List somewhere. From there we could provide a method for users to log themselves. Am I on the right track?
Yes, well an "event" is something like a System.Logger.LEVEL + message (+ maybe a code if we want some business logic to work off codes rather than message content).
The reason for doing this is because sometimes we want the configuration to load completely BEFORE any logging is used. This allows the configuration to put things into System Properties which is used to configure the actual logging.
The text was updated successfully, but these errors were encountered: