Re: Maintaining a set of Log4j configurations

That design should be fine but you will need to implement your own ContextSelector to locate the LoggerContext from the Map. You will also need to make sure the application id is available whenever something needs to locate the LoggerContext via the ContextSelector. As I have said previously, l

Maintaining a set of Log4j configurations

Hi, consider a logging server. Let's say, there's a REST service "log", accepting the following parameters: - applicationId - category - level - message The purpose here is to use the application id as identification of a log4j configuration. So, the implementation would look roughly

JDK 16 EA build 18 is now available

Hi Ralph, OpenJDK 16 Early Access build 18**is now available at http://jdk.java.net/16 * These early-access , open-source builds are provided under the o GNU General Public License, version 2, with the Classpath Exception . * Features: