|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
27/Jan/08 02:39 AM
|
|
The XMLLayout acts independently of the document encoding and a mixmatch can easily result in invalid files. To prevent the issue, it would be beneficial if all characters greater than 0x7F be represented using character entities.
In addition, the current XMLLayout would appear to not successfully handle logger names and other fields that contain special characters like <, >, ", etc. I believe that these same weaknesses affect log4j.
|
|
Description
|
The XMLLayout acts independently of the document encoding and a mixmatch can easily result in invalid files. To prevent the issue, it would be beneficial if all characters greater than 0x7F be represented using character entities.
In addition, the current XMLLayout would appear to not successfully handle logger names and other fields that contain special characters like <, >, ", etc. I believe that these same weaknesses affect log4j. |
Show » |
|
Bug
Resolved
Major
XML layout can be mismatched with document encoding
log4j has decided to not attempt to address encoding mismatch, you should use a UTF-8 or UTF-16 encoding when using an XMLLayout to avoid getting mangled characters.