- logback-dev - mailman3.qos.ch

[qos-ch/logback] 6e652c: docs on scopes
by Ceki Gulcu 02 Aug '12

02 Aug '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 6e652c781abd2c4e0b11150d89dfc7354165c6b7 https://github.com/qos-ch/logback/commit/6e652c781abd2c4e0b11150d89dfc73541… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-08-02 (Thu, 02 Aug 2012) Changed paths: M logback-core/src/test/java/ch/qos/logback/core/joran/action/DefinePropertyActionTest.java M logback-site/src/site/pages/manual/configuration.html Log Message: ----------- docs on scopes

1 0

[qos-ch/logback] 4ae089: minor refactoring
by Ceki Gulcu 02 Aug '12

02 Aug '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 4ae0892916216aec91386f298a1637247770f4f9 https://github.com/qos-ch/logback/commit/4ae0892916216aec91386f298a16372477… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-08-02 (Thu, 02 Aug 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/Logger.java M logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java M logback-core/src/main/java/ch/qos/logback/core/joran/GenericConfigurator.java M logback-core/src/test/java/ch/qos/logback/core/joran/SimpleConfigurator.java M logback-core/src/test/java/ch/qos/logback/core/joran/action/DefinePropertyActionTest.java M logback-examples/src/main/java/chapters/appenders/socket/ConsolePluginClient.java Log Message: ----------- minor refactoring

1 0

[JIRA] (LOGBACK-719) Provide a mechanism to specify an appender factory class
by Rich Mayfield (JIRA) 01 Aug '12

01 Aug '12

2 13

[qos-ch/logback-beagle] cbdd12: comment about buffer size
by Ceki Gulcu 01 Aug '12

01 Aug '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-beagle Commit: cbdd122d4eaa3ec9e1f87ea4a8f51c242f7f8a88 https://github.com/qos-ch/logback-beagle/commit/cbdd122d4eaa3ec9e1f87ea4a8f… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-08-01 (Wed, 01 Aug 2012) Changed paths: M ch.qos.logback.beagle/src/ch/qos/logback/beagle/visual/ClassicTISBuffer.java Log Message: ----------- comment about buffer size

1 0

Organizing loggers per function/mechanism rather than per class
by Cristian SPIESCU 30 Jul '12

30 Jul '12

Hello all, I would like to change the way messages are logged in my current application. Now, all the loggers are defined in the "classic" way: a logger per class, that is named according to the owning class. For the features/functions/mechanisms that span their execution among multiple classes, it's more convenient to organize the log per those specific roles that they play in the application. Let me give you an example. * Class: ServerEndpoint having 2 methods: deserialize(), executeLogic(). * Class: ServerLogicUnit having 2 similar methods: deserialize(), executeLogic(). I'd like both methods: ServerEndpoin.deserialize() and ServerLogicUnit.deserialize() (+ subclasses eventually) to use a logger, let's say: "server.processing.deserialization". In a similar way, ServerEndpoint.executeLogic() and ServerLogicUnit.executeLogic() would use "server.processing.execution". I see 2 solutions for this. 1) Have loggers that are registered like this: static public Logger loggerSerialization = LoggerFactory.getLogger("server.processing.deserialization"); static public Logger loggerExecution = LoggerFactory.getLogger("server.processing.execution"); This loggers are stored somewhere kind of globally, and different pieces of code, from various classes use them for logging. 2) I guess a solution can be found, even if the loggers are stored per class, using markers or MDC + some custom filtering logic. My question: what are the best practices in this area? Are there possible issues if I'll go for "Solution 1"? I'm realizing that I instantiate one logger per class somehow by reflex, not as result of a need. When I need to activate the log in a production application, to see what happens with a certain mechanism of the application, I end up in enabling debug or trace for the whole app. This shows me what I need, but it pollutes my log terribly. Thank you in advance for you feedback. Best regards, Cristian.

1 0

[qos-ch/logback-beagle] 4ac654: repopulate grid after filtering changes
by Ceki Gulcu 29 Jul '12

29 Jul '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-beagle Commit: 4ac654cb44f88440ea56349b68590093d9d7f428 https://github.com/qos-ch/logback-beagle/commit/4ac654cb44f88440ea56349b685… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-07-29 (Sun, 29 Jul 2012) Changed paths: R ch.qos.logback.beagle/src/ch/qos/logback/beagle/HideMain.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/LoggerTree.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMain.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMenuBuilder.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMenuSelectionListener.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/view/TableMediator.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/visual/ClassicTISBuffer.java Log Message: ----------- repopulate grid after filtering changes

1 0

[JIRA] (LOGBACK-726) Aggregating multiple logback.xml configurations
by Ryan (JIRA) 29 Jul '12

29 Jul '12

1 2

[qos-ch/logback-beagle] f3f30b: logger tree placed in the view
by Ceki Gulcu 28 Jul '12

28 Jul '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-beagle Commit: f3f30b390d139fb581b6807ee6a3f06c0ec67373 https://github.com/qos-ch/logback-beagle/commit/f3f30b390d139fb581b6807ee6a… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-07-28 (Sat, 28 Jul 2012) Changed paths: M ch.qos.logback.beagle.tests/src/ch/qos/logback/beagle/vista/MyMain.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/Constants.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/menu/DynamicMenuEnabler.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/menu/GridMenuBuilder.java R ch.qos.logback.beagle/src/ch/qos/logback/beagle/menu/MenuBuilder.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/menu/OnMenuSelectionAction.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/net/EventConsumerThread.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/net/LoggingEventSocketServer.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/LoggerTree.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMain.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMenuBuilder.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMenuSelectionListener.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/view/BeagleView.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/view/SashListener.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/view/TableMediator.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/visual/ClassicTISBuffer.java M logback-beagle.target Log Message: ----------- logger tree placed in the view

1 0

[qos-ch/logback-beagle] 25889e: ongoing work on logger tree
by Ceki Gulcu 27 Jul '12

27 Jul '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-beagle Commit: 25889ee19e9bff614649dd595765e8aef8b23c56 https://github.com/qos-ch/logback-beagle/commit/25889ee19e9bff614649dd59576… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-07-27 (Fri, 27 Jul 2012) Changed paths: A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/D-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/D-24x24.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/E-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/E-24x24.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/I-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/I-24x24.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/T-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/T-24x24.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/W-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/W-24x24.png M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/LoggerTree.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMain.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/util/ResourceUtil.java Log Message: ----------- ongoing work on logger tree

1 0

Logging plain text to an tcp socket
by Benjamin Leov 27 Jul '12

27 Jul '12

Hi Developers! Im looking for a way of connecting logback to nxlog. As nxlog does not have direct support for logback, the easiest way I can think of doing it would be via a plain text connection. However, without writing custom code (which isn't an option as I want to use this in many existing applications), I can see no way of doing that. Have I missed something? What would be really nice would be to allow the SocketAppender to take an encoder. Any help would be much appreciated! Regards, Ben

1 0