You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Carlos Icaza (JIRA)" <ji...@apache.org> on 2014/02/02 17:26:12 UTC
[jira] [Updated] (LOG4PHP-217) LoggerLayoutXml with enabled
log4jNamespace create extra "xml labels"
[ https://issues.apache.org/jira/browse/LOG4PHP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Icaza updated LOG4PHP-217:
---------------------------------
Attachment: LoggerLayoutXml_2.3.0.patch
This is the patch file generated by Meld 1.6
> LoggerLayoutXml with enabled log4jNamespace create extra "xml labels"
> ---------------------------------------------------------------------
>
> Key: LOG4PHP-217
> URL: https://issues.apache.org/jira/browse/LOG4PHP-217
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.3.0
> Environment: OS: Debian GNU/Linux 7.3 (virtualbox virtual machine)
> PHP: 5.4.4-14+deb7u7
> Apache: 2.2.22
> Hardware: Intel Celeron 2GHz, 2 MB RAM
> Reporter: Carlos Icaza
> Labels: patch
> Fix For: 2.3.0
>
> Attachments: LoggerLayoutXml_2.3.0.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> LoggerLayoutXml with enabled log4jNamespace create extra "xml labels"
> The logfile contains this xml labels:
> <log4j:eventSet ...>
> </log4j:eventSet>
> Some programs like Apache Chainsaw and Otroslogviewer are unable to parse the log file locally or remotely.
> I think that only events must be logged. I know that this component does not output a complete well-formed XML file. The output should be designed to be included as an external entity in a separate file to form a correct XML file.
> I removed this methods: getHeader() and getFooter() from file src/main/php/layouts/LoggerLayoutXml.php, and the above mentioned programs parse the log file successfully
> I created a patch using Meld 1.6.0, but there is no option to upload neither patch files nor screen capture images.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)