
|
If you were logged in you would be able to see more operations.
|
|
|
logback-core
Created: 30/Jun/09 04:09 PM
Updated: 30/Jun/09 04:09 PM
|
|
| Component/s: |
Appender
|
| Affects Version/s: |
0.9.15
|
| Fix Version/s: |
None
|
|
|
Environment:
|
Windows XP, Java 1.5 Sun JVM, Tomcat 5.0.27
|
|
|
I was expecting "message" implicit variable to contain the full message rendered by the %message or %msg from the pattern, but the recommanded way of logging,
using LOG.debug("I want to log an object {}", object); is only formatted in the event.getFormattedMessage(), event.getMessage <=> message, but only contains the "I want to log an object {}"
so if my matching string for the expression setting for the EvaluatorFilter is the dynamical part I can't never match my string, instead it got "{}".
So, it would be less confusing for users to find in the documentation an explicit information on what message variable contains, and does not contain!
Thank you
I would be happy to explain my point if you find it unclear or irrelevant.
|
|
Description
|
I was expecting "message" implicit variable to contain the full message rendered by the %message or %msg from the pattern, but the recommanded way of logging,
using LOG.debug("I want to log an object {}", object); is only formatted in the event.getFormattedMessage(), event.getMessage <=> message, but only contains the "I want to log an object {}"
so if my matching string for the expression setting for the EvaluatorFilter is the dynamical part I can't never match my string, instead it got "{}".
So, it would be less confusing for users to find in the documentation an explicit information on what message variable contains, and does not contain!
Thank you
I would be happy to explain my point if you find it unclear or irrelevant. |
Show » |
| There are no comments yet on this issue.
|
|