I see log4j -2 has renamed MDC ( and NDC) as "ThreadContext". https://logging.apache.org/log4j/2.x/manual/thread-context.html
I think this is slightly ahead of slf4j and logback, both of which still have MDC. I agree with you that log4j2 is the probably the best solution currently. -M On 1/30/2017 5:40 AM, Joern Kottmann wrote: > In other applications I usually try to add as much as possible context > information to the MDC, because that can help to find certain problems or > just understand what was going on. > > +1 on using MDC > > If we do a v3 release i would remove the old logging APIs if the intention > is not to use it anymore, users can rather quickly migrate to the new > logging API of our choice. Also log4j2 is quite nice to use and is probably > the best solution out there currently. > > Jörn > > On Sun, Jan 29, 2017 at 4:47 PM, Richard Eckart de Castilho <[email protected]> > wrote: > >> On 24.01.2017, at 21:48, Marshall Schor <[email protected]> wrote: >>> 1) keep the current UIMA logging facade and framework, for backwards >> compatibility. >> >> uimaFIT adds a getLogger() method to its base-classes for reader and >> engines because >> getting the logger via the context is just an extra step >> (getContext().getLogger().error(...) vs >> getLogger().error(...)). >> >> It could be considered adding logging methods directly to the UIMA >> component base-classes, such >> that one simply would call "error(...)"? Or introducing a short getter >> method (log().error(...)))? >> >> Cheers, >> >> -- Richard
