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
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
