PatternLayout isn’t really designed to use an alternate implementation of
PatternParser. Why do you need one? A custom Layout wouldn’t normally use a
PatternParser, only PatternLayout and you shouldn’t need to modify that either.
Just create a new PatternConverter that does what you need it to d
Once you've implemented a LogEventPatternConverter which overrides
"handlesThrowable" to return true, you will also need to use that pattern in
the PatternLayout pattern. This can be a little bit confusing since the pattern
layout will automatically add a default throwable pattern converter to t
Did you include the @ConverterKeys annotation on your converters? You
shouldn't need to make a new layout I think.
On Wed, 22 May 2019 at 06:18, Gaurav wrote:
>
>
>
> On 2019/05/16 14:59:56, Matt Sicker wrote:
> > Instead of extending the plugin classes, you can create your own
> > plugins. Patt
On 2019/05/16 14:59:56, Matt Sicker wrote:
> Instead of extending the plugin classes, you can create your own
> plugins. PatternConverters are relatively trivial plugins, so I
> wouldn't worry too much about code duplication.
>
> I could be missing a feature, though.
>
> On Thu, 16 May 2019
