After reducing the bundle composite I can say that this issue only affacts the log4j2-api and the log4j2-core, nothing else.
I conclude that this could be a ClassLoader-issue. I think that the log4j2-api uses the bundle-classloader whereas the implementation is created by the bootstrap-classloader. Thus, the instance is not assignable or castable. Further investigations are necessary. How can I print the classloader used by the implementation and by the api? -- View this message in context: http://apache-logging.6191.n7.nabble.com/Log4jContextFactory-does-not-implement-LoggerContextFactory-tp40136p40151.html Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
