[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430613#comment-15430613
]
Ralph Goers commented on LOG4J2-905:
We have no plans to do that as this should give you exactly what
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430209#comment-15430209
]
Luca Burgazzoli commented on LOG4J2-905:
In addition to this option, will you add a global option
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427670#comment-15427670
]
Gary Gregory commented on LOG4J2-905:
-
I've isolated the behavior in a unit test:
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427544#comment-15427544
]
Gary Gregory commented on LOG4J2-905:
-
What happens if you say:
{code:java}
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427524#comment-15427524
]
Gary Gregory commented on LOG4J2-905:
-
Agreed, that's cool. Then later we can think of adding
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427486#comment-15427486
]
Remko Popma commented on LOG4J2-905:
I like this idea of having an option that disables lookups.
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426860#comment-15426860
]
Ralph Goers commented on LOG4J2-905:
IMO, the correct solution is to add an option to %msg such as
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426800#comment-15426800
]
Gary Gregory commented on LOG4J2-905:
-
Thinking out-loud: If we provide/document a way to disable
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426737#comment-15426737
]
Luca Burgazzoli commented on LOG4J2-905:
Cam just tries to log the route definition as it is,
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426748#comment-15426748
]
Michael Gysel commented on LOG4J2-905:
--
Hi
I'm out of office until September 19th and I will not
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303656#comment-15303656
]
Michael Gysel commented on LOG4J2-905:
--
I just found this issue as well.
> Out of curiosity, what
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302130#comment-15302130
]
Ralph Goers commented on LOG4J2-905:
Out of curiosity, what does the application expect to happen when
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187691#comment-15187691
]
moritz löser commented on LOG4J2-905:
-
the problem is not about camel, the problem is that you can't
[
https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187440#comment-15187440
]
Matt Sicker commented on LOG4J2-905:
Doesn't camel log out a pre-formatted statement after
14 matches
Mail list logo