- logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCLASSIC-281) Don't evaluate formattedMessage in LoggingEvent constructor
by Andrew Brett (JIRA) 16 Feb '12

16 Feb '12

Don't evaluate formattedMessage in LoggingEvent constructor ----------------------------------------------------------- Key: LBCLASSIC-281 URL: http://jira.qos.ch/browse/LBCLASSIC-281 Project: logback-classic Issue Type: Improvement Affects Versions: 0.9.29 Reporter: Andrew Brett Assignee: Logback dev list Whenever a ch.qos.logback.classic.spi.LoggingEvent is constructed, MessageFormatter.arrayFormat(...) is called, and the formattedMessage member variable assigned. This involves calling toString() on all arguments in argArray, which can be slow, and occurs even if the formattedMessage is not part of any appender layouts. For my project's purposes, I have a custom formatter which only outputs an abbreviated string form of certain objects with expensive toString() methods; however, I am still paying the overhead in the toString() calls, since they're made even when getFormattedMessage() is never called. Note that I don't control the source of the objects with expensive toString() methods, nor do I control the source everywhere they're logged, so I can't simply change them directly. formattedMessage is already evaluated lazily in getFormattedMessage(), so the only side effect of this change is the introspection of argsArray to look for a Throwable at the end, which is a trivial operation to perform separately. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 3

[android] support for SMTPAppender: almost there?
by Enrico Spinielli 11 Feb '12

11 Feb '12

Hi, it looks like I am close to be able to add support for SMTPAppender. I modified the build.xml to include the relevant code, re-introduced the tests (SocketAppenderTest.class, DilutedSMTPAppenderTest.class, SMTPAppender_GreenTest.class) and (properly?) set the bootclasspath to use the android version of javax.mail (see my previous post on SMTPAppender). I forked logback-android and pushed my changes in https://github.com/espinielli/logback-android It looks like the features I am interested in are ok, since I am getting only html/htmlLong test cases failing (see below) and I am not interested in sending html formatted logs via email. I will try this version out on my android app soon and provide feedback on this list. Of course I will welcome any feedbacks from anyone on what I did, i.e. mistakes, bugs ... fixes and ideas are welcome too. Thanks in advance Bye Enrico When I run the tests I get html/htmlLong failing with the following: [junit] Testcase: html took 260.281 sec [junit] Caused an ERROR [junit] Unexpected end of file from server Nested exception: Unexpected end of file from server [junit] org.dom4j.DocumentException: Unexpected end of file from server Nested exception: Unexpected end of file from server [junit] at org.dom4j.io.SAXReader.read(SAXReader.java:484) [junit] at org.dom4j.io.SAXReader.read(SAXReader.java:343) [junit] at ch.qos.logback.classic.net.SMTPAppender_GreenTest.html(Unknown Source) [junit] Nested exception: [junit] java.net.SocketException: Unexpected end of file from server [junit] at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:777) [junit] at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:640) [junit] at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:774) [junit] at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:640) [junit] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195) [junit] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:677) [junit] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1315) [junit] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1252) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.startPE(XMLDTDScannerImpl.java:722) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.skipSeparator(XMLDTDScannerImpl.java:2069) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDecls(XMLDTDScannerImpl.java:2032) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDTDExternalSubset(XMLDTDScannerImpl.java:320) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1203) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1090) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1003) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) [junit] at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) [junit] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) [junit] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) [junit] at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) [junit] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) [junit] at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) [junit] at org.dom4j.io.SAXReader.read(SAXReader.java:465) [junit] at org.dom4j.io.SAXReader.read(SAXReader.java:343) [junit] at ch.qos.logback.classic.net.SMTPAppender_GreenTest.html(Unknown Source) [junit] [junit] Testcase: htmlLong took 736.286 sec [junit] Caused an ERROR [junit] Unexpected end of file from server Nested exception: Unexpected end of file from server [junit] org.dom4j.DocumentException: Unexpected end of file from server Nested exception: Unexpected end of file from server [junit] at org.dom4j.io.SAXReader.read(SAXReader.java:484) [junit] at org.dom4j.io.SAXReader.read(SAXReader.java:343) [junit] at ch.qos.logback.classic.net.SMTPAppender_GreenTest.htmlLong(Unknown Source) [junit] Nested exception: [junit] java.net.SocketException: Unexpected end of file from server [junit] at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:777) [junit] at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:640) [junit] at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:774) [junit] at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:640) [junit] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195) [junit] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:677) [junit] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1315) [junit] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1252) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.startPE(XMLDTDScannerImpl.java:722) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.skipSeparator(XMLDTDScannerImpl.java:2069) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDecls(XMLDTDScannerImpl.java:2032) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDTDExternalSubset(XMLDTDScannerImpl.java:320) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1203) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1090) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1003) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) [junit] at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) [junit] at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) [junit] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) [junit] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) [junit] at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) [junit] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) [junit] at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) [junit] at org.dom4j.io.SAXReader.read(SAXReader.java:465) [junit] at org.dom4j.io.SAXReader.read(SAXReader.java:343) [junit] at ch.qos.logback.classic.net.SMTPAppender_GreenTest.htmlLong(Unknown Source) -- Enrico Spinielli "Do Androids dream of electric sheep?"— Philip K. Dick "Hear and forget; see and remember;do and understand."—Mitchel Resnick "He who refuses to do arithmetic is doomed to talk nonsense."—John McCarthy

1 1

[JIRA] Created: (LBGENERAL-51) Implementation-Version missed in Manifest-File
by Rudolf Pfister (JIRA) 10 Feb '12

10 Feb '12

Implementation-Version missed in Manifest-File ---------------------------------------------- Key: LBGENERAL-51 URL: http://jira.qos.ch/browse/LBGENERAL-51 Project: logback-general Issue Type: Improvement Components: build-structure Affects Versions: 1.0.0 Reporter: Rudolf Pfister Assignee: Logback dev list Priority: Minor In the Manifest-File of the logback-*.jar-files there are np properties like - Implementation-Version, Implementation-Title, Implementation-Vendor - Specification-Version, Specification-Title, Specification-Vendor These Properties are useful to retreive Information about an package via the java.lang.Package-class. Example: System.out.println( org.slf4j.Logger.class.getPackage() .getImplementationVersion()); System.out.println( ch.qos.logback.core.Appender.class.getPackage() .getImplementationVersion()); First sysout returns e.g. 1.6.4, whereas second sysout returns null. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[GIT] Logback-audit: logging for events with business significance. branch master updated. v_0.5-1-g9afd68d
by git-noreply＠pixie.qos.ch 08 Feb '12

08 Feb '12

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback-audit: logging for events with business significance.". The branch, master has been updated via 9afd68d50124fd3a1e3841df44a8d69df81c8b8d (commit) from 50428a9363b4269d356bdee362bc10d89baf2207 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://github.com/ceki/logback-audit/commit/9afd68d50124fd3a1e3841df44a8d69… commit 9afd68d50124fd3a1e3841df44a8d69df81c8b8d Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Feb 8 19:32:46 2012 +0100 - added missing audit-server-generator folder to assembly - minor edits diff --git a/audit-client/pom.xml b/audit-client/pom.xml index 5531df1..23a2dba 100644 --- a/audit-client/pom.xml +++ b/audit-client/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>audit-parent</artifactId> - <version>0.5</version> + <version>0.6</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/audit-common/pom.xml b/audit-common/pom.xml index aab3f12..9079470 100644 --- a/audit-common/pom.xml +++ b/audit-common/pom.xml @@ -8,7 +8,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>audit-parent</artifactId> - <version>0.5</version> + <version>0.6</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/audit-examples/pom.xml b/audit-examples/pom.xml index e6a0352..b802ec2 100644 --- a/audit-examples/pom.xml +++ b/audit-examples/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>audit-parent</artifactId> - <version>0.5</version> + <version>0.6</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/audit-server-generator/build.xml b/audit-server-generator/build.xml old mode 100644 new mode 100755 index 08adab1..15469e3 --- a/audit-server-generator/build.xml +++ b/audit-server-generator/build.xml @@ -14,14 +14,15 @@ <target name="input"> - <input addproperty="group"> - - Please enter the name of the group for this server: </input> - - <input addproperty="project"> - - Please enter the project name for this server:</input> +  +  + <input addproperty="project" + message="Please enter the project name for this server: "/> </target> <target name="overwriteCheck"> diff --git a/audit-server-generator/template/pom.xml b/audit-server-generator/template/pom.xml old mode 100644 new mode 100755 index 014f464..58ead76 --- a/audit-server-generator/template/pom.xml +++ b/audit-server-generator/template/pom.xml @@ -2,7 +2,7 @@ <project> <modelVersion>4.0.0</modelVersion> - <groupId>@GROUP_NAME@</groupId> + <groupId>org.change.me</groupId> <artifactId>@PROJECT_NAME@</artifactId> <packaging>war</packaging> <name>@PROJECT_NAME@</name> @@ -40,17 +40,9 @@ <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> - <version>0.9.9</version> + <version>1.0.0</version> </dependency> -  - <dependency> <groupId>hsqldb</groupId> <artifactId>hsqldb</artifactId> diff --git a/audit-server/pom.xml b/audit-server/pom.xml index 855f40c..f08e4e6 100755 --- a/audit-server/pom.xml +++ b/audit-server/pom.xml @@ -4,7 +4,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>audit-parent</artifactId> - <version>0.5</version> + <version>0.6</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/audit-site/pom.xml b/audit-site/pom.xml index 2b22f84..5e2a4fc 100755 --- a/audit-site/pom.xml +++ b/audit-site/pom.xml @@ -6,7 +6,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>audit-parent</artifactId> - <version>0.5</version> + <version>0.6</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/audit-site/src/site/pages/templates/footer.js b/audit-site/src/site/pages/templates/footer.js index 08094bd..0a2e162 100755 --- a/audit-site/src/site/pages/templates/footer.js +++ b/audit-site/src/site/pages/templates/footer.js @@ -4,7 +4,7 @@ document.write('<table class="footer" border="0">') document.write('<tr>') -document.write('<td valign="top">Copyright © 2011 <a href="http://www.qos.ch/">QOS.ch</a></td>') +document.write('<td valign="top">Copyright © 2012 <a href="http://www.qos.ch/">QOS.ch</a></td>') document.write(' <td rowspan="2">') document.write(' <script type="text/javascript" src="http://www.ohloh.net/p/586885/widgets/project_users.js"></script>') diff --git a/pom.xml b/pom.xml index 1883b39..a9d38b6 100755 --- a/pom.xml +++ b/pom.xml @@ -6,7 +6,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>audit-parent</artifactId> - <version>0.5</version> + <version>0.6</version> <packaging>pom</packaging> <name>Logback Audit Parent</name> diff --git a/src/main/assembly/dist.xml b/src/main/assembly/dist.xml index c1ec63c..e7dd6e7 100755 --- a/src/main/assembly/dist.xml +++ b/src/main/assembly/dist.xml @@ -54,6 +54,21 @@ <exclude>*.bak</exclude> </excludes> </fileSet> + + <fileSet> + <directory>audit-server-generator/</directory> + <outputDirectory>audit-server-generator/</outputDirectory> + <includes> + <include>pom.xml</include> + <include>build.xml</include> + <include>template/</include> + </includes> + <excludes> + <exclude>*.bak</exclude> + </excludes> + </fileSet> + +  <fileSet> <directory>audit-common/src/</directory> ----------------------------------------------------------------------- Summary of changes: audit-client/pom.xml | 2 +- audit-common/pom.xml | 2 +- audit-examples/pom.xml | 2 +- audit-server-generator/build.xml | 15 ++++++++------- audit-server-generator/template/pom.xml | 12 ++---------- audit-server/pom.xml | 2 +- audit-site/pom.xml | 2 +- audit-site/src/site/pages/templates/footer.js | 2 +- pom.xml | 2 +- src/main/assembly/dist.xml | 15 +++++++++++++++ 10 files changed, 32 insertions(+), 24 deletions(-) mode change 100644 => 100755 audit-server-generator/build.xml mode change 100644 => 100755 audit-server-generator/template/pom.xml hooks/post-receive -- Logback-audit: logging for events with business significance.

1 0

[JIRA] Created: (LBCORE-245) logback 0.9.30 fileNamePattern does not create missing directories
by Vedavalli Kanala (JIRA) 06 Feb '12

06 Feb '12

logback 0.9.30 fileNamePattern does not create missing directories ------------------------------------------------------------------ Key: LBCORE-245 URL: http://jira.qos.ch/browse/LBCORE-245 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.30 Reporter: Vedavalli Kanala Assignee: Logback dev list We are using logback 0.9.30. In our logback configuration we have the need to create an appender that rolls over every day and the archives are stored in a separate directory. <fileNamePattern> tag does not seem to create the missing directories in the path. However, <File> tag under the <appender> seems to work fine. This is the sample configuration we have: <appender name="ABC" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/var/abc/abc.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>/var/abc/abc-archive/abc.%d{yyyy-MM-dd'T'HH}.log.gz</fileNamePattern> <maxHistory>365</maxHistory> </rollingPolicy> <encoder> <pattern>%msg%n</pattern> </encoder> </appender> "/var/abc/abc-archive" directory doesn't exist on the file system and i would expect that logback would create the missing directory. Please let us know if there is any piece missing in the configuration that would do that job or if its a genuine bug and would get fixed sometime soon. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[android] tests failing: destfile jar incorrect
by Enrico Spinielli 04 Feb '12

04 Feb '12

Hi, I did clone latest logback-android, setup ant.properties and tried to build/test. Tests were not running correctly: classNotFound... I found out that the build-test target wrongly specifies out.jar as destfile instead of test.out.jar With this fix, I am able to successfully run the tests (even if they are not all SUCCESSful) Hope it helps Bye -- Enrico Spinielli "Do Androids dream of electric sheep?"— Philip K. Dick "Hear and forget; see and remember;do and understand."—Mitchel Resnick "He who refuses to do arithmetic is doomed to talk nonsense."—John McCarthy

2 1

[JIRA] Created: (LBCORE-146) SiftingAppender TimeBasedRollingPolicy MaxHistory not deleting old files
by Hrotkó Gábor (JIRA) 03 Feb '12

03 Feb '12

SiftingAppender TimeBasedRollingPolicy MaxHistory not deleting old files ------------------------------------------------------------------------ Key: LBCORE-146 URL: http://jira.qos.ch/browse/LBCORE-146 Project: logback-core Issue Type: Bug Components: Rolling Affects Versions: 0.9.18 Environment: linux64, jdk1.6.0_17-b04, apache-tomcat-6.0.24 Reporter: Hrotkó Gábor Assignee: Logback dev list When I use SiftingAppender with TimeBasedRollingPolicy, old files does not get deleted when the MaxHistory is set. logback.xml snipet: <configuration debug="true" scan="true" scanPeriod="5 seconds"> <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator> <Key>userid</Key> <DefaultValue>base</DefaultValue> </discriminator> <sift> <appender name="FILE-${userid}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>/usr/local/tomcat6/logs/myLog_${userid}.log</File> <Append>false</Append> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d [%thread] %level %mdc %logger.%method:%line - %msg%n</Pattern> </layout> <RollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>/usr/local/tomcat6/logs/myLog_${userid}.%d{yyyy-MM-dd}.log</FileNamePattern>  <MaxHistory>2</MaxHistory> </RollingPolicy> </appender> </sift> </appender> ... With the config above, the files gets sifted and rolled well, but old files not deleted. When I change the filenames, and delete the ${userid} sifting, it works well. ... <File>/usr/local/tomcat6/logs/myLog.log</File> ... <FileNamePattern>/usr/local/tomcat6/logs/myLog.%d{yyyy-MM-dd}.log</FileNamePattern> ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 1

[JIRA] Created: (LBCLASSIC-321) set root level and log home (base) path for file appenders using MDC (context?) properties
by Miroslav Obradovic (JIRA) 29 Jan '12

29 Jan '12

set root level and log home (base) path for file appenders using MDC (context?) properties ------------------------------------------------------------------------------------------ Key: LBCLASSIC-321 URL: http://jira.qos.ch/browse/LBCLASSIC-321 Project: logback-classic Issue Type: New Feature Components: joran Reporter: Miroslav Obradovic Assignee: Logback dev list would it be possible to keep application depend only on slf4j at compile time, but still be able to pass context properties to logback.xml through MDC in a standalone app, assuming I take care not to get/access any loggers until I put the context properties into MDC? (I am aware that I could programatically get the root logger by name and cast it to logback Logger, and then set the level, and add a file appender, but this would require logback jars at compile time) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 3

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch master updated. v_1.0.0-66-g0877b9c
by git-noreply＠pixie.qos.ch 27 Jan '12

27 Jan '12

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via 0877b9c3e93e159adce108834e608b67929ec74d (commit) from 1b13450172993fdc8597e3a0e1bd11fb9a9459bf (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=0877b9c3e93e159adce10883… http://github.com/ceki/logback/commit/0877b9c3e93e159adce108834e608b67929ec… commit 0877b9c3e93e159adce108834e608b67929ec74d Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Jan 27 22:02:43 2012 +0100 typo fix diff --git a/logback-site/src/site/pages/manual/architecture.html b/logback-site/src/site/pages/manual/architecture.html index 9793c71..8cc282f 100644 --- a/logback-site/src/site/pages/manual/architecture.html +++ b/logback-site/src/site/pages/manual/architecture.html @@ -61,7 +61,7 @@ <a href="../access.html">access module documentation</a>. </p> - <p>In the reminder of this document, we will write "logback" to + <p>In the remainder of this document, we will write "logback" to refer to the logback-classic module. </p> ----------------------------------------------------------------------- Summary of changes: .../src/site/pages/manual/architecture.html | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

non serializing SocketAppender
by Enrico Spinielli 16 Jan '12

16 Jan '12

Hi, I am looking for some direction or historical memories about the possibility to have a SocketAppender that does not serialize the payload. (This is to be able to read at the other end with a non Java based program...) Browsing the code it seems that one possibility is to have a derived class of SocketAppender to implement getPST() to return a PreSerializationTransformer that does no transformations, but then the event object is (/seems to be) written to an ObjectOutputStream. This means, I guess, that even if you write a custom serialization code and avoid any transformations, in the end, the event will still be written to the pipe as a java object. Please comment on the above statements and provide directions or examples for further explorations. Thanks a lot in advance Bye -- Enrico Spinielli "Do Androids dream of electric sheep?"— Philip K. Dick "Hear and forget; see and remember;do and understand."—Mitchel Resnick "He who refuses to do arithmetic is doomed to talk nonsense."—John McCarthy

1 0