Dear all,
After spending half a day on this I have decide to try luck on the official
mailing list, hopefully some dev can throw some light over this.
I’m trying to use a wrapper over a Logger object to restrict the methods of the
API to the ones on my interface, for example:
class Log4JLogger
When you make a custom Logger wrapper, you need to use the logMessage()
methods that include the fqcn string which should be the fully qualified
class name of the logger wrapper. See AbstractLogger for an example.
On 10 September 2016 at 13:57, Juan Fuentes
wrote:
> Dear all,
>
> After spending
I should note that you might want to use ExtendedLoggerWrapper in this
scenario as the methods are protected otherwise that I just mentioned.
On 10 September 2016 at 14:03, Matt Sicker wrote:
> When you make a custom Logger wrapper, you need to use the logMessage()
> methods that include the fqc
Yes, you use ExtendedLoggerWrapper and pass the fully qualified class name of
your wrapper class on the logMessage call. I seem to recall there is an even
easier way but it escapes me and I don’t see it documented on the web site.
Ralph
> On Sep 10, 2016, at 12:06 PM, Matt Sicker wrote:
>
> I
If there's an easier way to do it, that'd be cool, but all the bridges in
log4j itself use ExtendedLoggerWrapper as it is.
On 10 September 2016 at 14:35, Ralph Goers
wrote:
> Yes, you use ExtendedLoggerWrapper and pass the fully qualified class name
> of your wrapper class on the logMessage call
I seem to recall Remko had some magic tool that creates the wrapper for you.
Ralph
> On Sep 10, 2016, at 12:44 PM, Matt Sicker wrote:
>
> If there's an easier way to do it, that'd be cool, but all the bridges in
> log4j itself use ExtendedLoggerWrapper as it is.
>
> On 10 September 2016 at 14:
Thanks Matt and Ralph,
I have extended ExtendedLoggerWrapper and it seems to work. Let’s hope I don’t
stumble against other peculiarities.
Thanks again!
Juan
> On 10 Sep 2016, at 21:44, Matt Sicker wrote:
>
> If there's an easier way to do it, that'd be cool, but all the bridges in
> log4j it
The easier way is to use the wrapper generator tool included in log4j. The tool
is intended to be used with custom log levels and is documented here:
https://logging.apache.org/log4j/2.x/manual/customloglevels.html#AddingOrReplacingLevels
I should add this question to the faq page, this is at le
Do we have documentation on making custom Loggers?
Ralph
> On Sep 10, 2016, at 5:09 PM, Remko Popma wrote:
>
> The easier way is to use the wrapper generator tool included in log4j. The
> tool is intended to be used with custom log levels and is documented here:
> https://logging.apache.org/l
I should have looked at your link first. It seems rather odd to find custom
logger documentation under custom levels, and I didn’t see it in the table of
contents - probably because I didn’t think to click on that.
Ralph
> On Sep 10, 2016, at 11:39 PM, Ralph Goers wrote:
>
> Do we have docum
The focus of that logger wrapper generator is on the convenience methods to
generate for a new log level, that is why the tools is documented under
custom levels.
This still makes sense to me, but I've seen this question several times now
so you are certainly not the only one who didn't find the d
11 matches
Mail list logo
