ppkarwasz commented on issue #1741: URL: https://github.com/apache/logging-log4j2/issues/1741#issuecomment-1761077363
Theoretically the Log4j API (unlike SLF4J 2.x) and its implementations can find each other in an OSGi environment without a Service Loader Mediator. Since I never developed OSGi applications, I don't know how common Apache Aries SPI Fly is in modern OSGi apps. If it is a _de facto_ standard, we can remove a lot of custom code and just rely on it. Anyway Log4j's behavior does not provide any advanced OSGi features: the Log4j API binds with a single implementation when the bundle is started and changing or upgrading the backend at runtime is impossible. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
