|
From: Colin D. <co...@ma...> - 2022-03-04 21:14:04
|
Nope, sorry On 3/4/22 12:28, Robert Nicholson wrote: > QFJ Documentation:http://www.quickfixj.org/documentation/ > QFJ Support:http://www.quickfixj.org/support/ > > > > Have you done it with a programmatically created appender? > > All works on my side when I’m using a statically created appender. > > The idea is to not have you statically create appender definition in > .xml for each quickfixj.msg.Incoming/Outgoing but > rather programmatically create a logger and appender for each. > > With 1.x this works without issue but with 1.x you don’t have to > completely trash the existing log4j config and you > can “hang” programmatically created appenders off an existing > statically created logger. ie. quickfixj.msg > > But with 2.x you need to reconfigure the log4j each time you make > change and so there’s as possibility that by the time you have done > that that Quickfix SLF4J is not aware of those loggers. Even though in > my case I believe I’m configuring log4j 2.x _prior_ to the SLF4J that > runs in Quickfix via SLF4JLog > > Also, has anybody succeed in the above when using logback? > >> On Mar 4, 2022, at 9:51 AM, Robert Nicholson >> <rob...@gm...> wrote: >> >> So I’m on an older version of quickfix pre 1.6 >> >> Does anybody know if it’s straightforward to get the SLF4J->Log4J2 >> working once you’re application supports Log4J2? >> >> Is there any changes needed with QuickFixJ code to use different >> SLF4J api when using Log4J2? >> >> Cheers. > > > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users -- Colin DuPlantis Chief Architect, Marketcetera Download, Run, Trade https://www.marketcetera.com |