Community
Participate
Working Groups
In E4Application class the WorkbenchLogger is added to the application context regardless of which ILoggerProvider is set. This is done in method createDefaultContext() after calling createDefaultHeadlessContext(). Using the ILoggerProvider to set a logger to the context would provide the possibility to set an own ILogger via setting a ILoggerProvider in the bundle activator of the application.
Sounds reasonable. Would you be able to provide a Gerrit review for that, so that we can code review your suggestion? See http://www.vogella.com/articles/Gerrit/article.html#eclipsegerritcontribution for an introduction to Gerrit contributions for Eclipse.
I think the ILoggerProvider does not really fit, as it requires a Class<?>. The "root" logger for the application is currently not instantiated with any specific class. I therefore suggest to: - Check if a Logger is existing in the context (service or app context) - If so, use this one - If not, instantiate the default one as before This would enable to replace the Logger just by registering an OSGi service or a context function.
Would the proposed solution solve your issue?
