ranger2025 commented on issue #3357: URL: https://github.com/apache/logging-log4j2/issues/3357#issuecomment-2578652545
@vy, thank you very much for sharing this information. I understand what you are talking about performance, but we plan to use it only for testing and debugging purposes. At least, now. However, it is necessary to find a solution for this problem, because module name without specifying the layer doesn't give a lot. I want to underline it, because it is very important. We have an application with plugins where plugin are added/removed dynamically. For for this plugins we use `ModuleLayer`s. So, we have the following layer configuration: ``` boot layer / main app ├── child layer 1 / plugin foo │ ├── moduleA │ ├── moduleC │ └── moduleX ├── child layer 2 / plugin bar │ ├── moduleS │ ├── moduleV │ └── moduleX └ etc ``` As you see, in this configuration the same module is used by both plugins. So, when we want to get messages of the `moduleX` we definitely want to get them for getting messages of concrete plugin. That's why I say it is important to get not only module name, but also some ID of the layer. If it is not possible to get layer instance, I can try to get it from `ClassLoader`, because when a new layer is created we can get its loaders. But I am not sure, how it will work with custom classloaders. Above I posted an example with `ClassLoaderContextSelector` but I am not sure that this is the way I should go. That's why I asked for help. -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
