ppkarwasz commented on issue #3159: URL: https://github.com/apache/logging-log4j2/issues/3159#issuecomment-2469785110
I am seriously considering deprecating `AsyncWaitStrategyFactoryConfig`. I will discuss it with the other maintainers (especially @remkop, who introduced it), but it could probably be replaced with the [`log4j2.asyncLoggerConfigWaitStrategy`](https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.asyncLoggerConfigWaitStrategy) Log4j configuration property. The presence of both a Log4j configuration property and a direct child of `<Configuration>` IMHO needlessly complexifies the logic to determine which waiting strategy to use. In `main` we have a simple DI system and the [`WaitStrategy` beans](https://github.com/apache/logging-log4j2/blob/main/log4j-async-logger/src/main/java/org/apache/logging/log4j/async/logger/internal/AsyncLoggerDefaultBundle.java) are the only ones that need a `Configuration` parameter. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
