Hello! I'm playing with logback and its eclipse plugin (ch.qos.logback.eclipse_1.1.0.zip) and for me it miss 2 features: 1) In "Logback View Filters" window it would be more user frendly to use comboboxes for slecting "Action on match" and "Action on mismatch" instead of text fields. 2) In "Logback View Filters" window it would be really useful to add column "Active"(or "Use" or smth. like that) in table with expressions to activate/deactivate some filters without deleting them. Alexey Kuznetsov kuaw26@mail.ru
I'm using LOGBack as slf4j implementation together with the bridges between legacy APIs and LOG4J in my OSGI enterprise app - I'm also using my own bridge between OSGI LogServices and SLF4J. I like the Markers from LOGBack and use them to log the OSGI Bundle- and Sercvice Names. All will be documented in my blog (the first 3 parts of my blog series "Logging in OSGI Enterprise Applications" are published till now) Now I'm interested to see the differences between Log4J and LOGBack. I already know about the Markers, which are important for me - are there any other differences ? thx ekke -- ekkehard gentz software-architect erp-consultant max-josefs-platz 30, D-83022 rosenheim, germany mailto:ekkehard@gentz-software.de homepage: http://www.gentz-software.de opensource: http://ekkehard.org blog (en): http://ekkes-corner.org blog (de): http://ekkes-ecke.org skype: ekke.gentz Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490
While the general archirecture is very similar, there are many differences. See http://svn.qos.ch/repos/logback/trunk/logback-site/src/site/resources/logbac... for a short presentation on logback. (The presentation used to be called "Ten reasons to switch to logback". IMHO, the higher activity seen in logback compared to log4j may be your most important reason to switch. ekkehard wrote:
I'm using LOGBack as slf4j implementation together with the bridges between legacy APIs and LOG4J in my OSGI enterprise app - I'm also using my own bridge between OSGI LogServices and SLF4J.
I like the Markers from LOGBack and use them to log the OSGI Bundle- and Sercvice Names.
All will be documented in my blog (the first 3 parts of my blog series "Logging in OSGI Enterprise Applications" are published till now)
Now I'm interested to see the differences between Log4J and LOGBack. I already know about the Markers, which are important for me - are there any other differences ?
thx
ekke
--
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch
Ceki Gulcu schrieb:
While the general archirecture is very similar, there are many differences. See
http://svn.qos.ch/repos/logback/trunk/logback-site/src/site/resources/logbac...
for a short presentation on logback. (The presentation used to be called "Ten reasons to switch to logback". thx IMHO, the higher activity seen in logback compared to log4j may be your most important reason to switch.
the main reason why I was asking about the real differences: I made my decision to use SLF4J as API and to use LOGBack as implementation. ...runs all inside OSGI Enterprise (client/server) application based on: Eclipse Equinox, Eclipse Riena, Easybeans / Hibernate etc. so I'm using bundles with the bridges between slf4j and log4j, jcl, jul and also wrote my osgi-over-slf4j bundle as bridge between OSGI log services, OSGI framework events, OSGI bundle events... all works well ...but there was a question in my blog why I'm not using PAX-Logging as bridge to other legacy logging frameworks. but PAX Logging uses Log4J as implementation and I'm working on my next blog entries and wanted to provide a matrix to compare features of log4j and logback ekke
participants (3)
-
Ceki Gulcu -
ekkehard -
Алексей Кузнецов