[
https://issues.apache.org/jira/browse/LOG4PHP-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806265#action_12806265
]
Christian Grobmeier commented on LOG4PHP-87:
--------------------------------------------
If I got you correct - chainsaw does not need a header like:
<log4j:event logger="TEST" level="ERROR" thread="503" timestamp="1264750453681">
That sounds somehow wrong to me - can you explain more
That is the complete output:
<log4j:event logger="TEST" level="ERROR" thread="503"
timestamp="1264750453681">
-<log4j:message><![CDATA[testmessage]]></log4j:message>
-<log4j:locationInfo class="LoggerLoggingEvent" file="NA" line="NA"
method="getLocationInformation" />
</log4j:event>
> Switch off headers for Chainsaw when using log4jNamespace = true
> ----------------------------------------------------------------
>
> Key: LOG4PHP-87
> URL: https://issues.apache.org/jira/browse/LOG4PHP-87
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.0
> Reporter: Carsten
> Fix For: 2.1
>
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> when trying to export Logging Events to Chainsaw through
> LoggerAppenderSocket Chainsaw has got problems with
> the header and footer created in LoggerLayoutXml.php Line 106
> (getHeader()) and 162 (getFooter()) .
> I then inserted a return at the top of both methods in case that
> log4jNamespace has been set to true in properties file:
> if ($this->getLog4jNamespace()) {
> return;
> }
> This solves this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
