-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
None
-
generic
-
generic
A DESCRIPTION OF THE PROBLEM :
Everything in Java has its own name — classes, interfaces, modules, etc. But ModuleLayers do not. And this creates serious problems. For example, when working with a multi-layer configuration, it becomes very difficult to retrieve log events for a specific layer.
The reason is that we cannot use a specific name that could be shared across different libraries. For instance, if we use log4j2, it provides the module name in the properties of a LogEvent, but it cannot provide a unique layer name because such a name simply does not exist.
Therefore, I propose adding such a property to layers. For example, it can be name, UUID, ID etc.
Everything in Java has its own name — classes, interfaces, modules, etc. But ModuleLayers do not. And this creates serious problems. For example, when working with a multi-layer configuration, it becomes very difficult to retrieve log events for a specific layer.
The reason is that we cannot use a specific name that could be shared across different libraries. For instance, if we use log4j2, it provides the module name in the properties of a LogEvent, but it cannot provide a unique layer name because such a name simply does not exist.
Therefore, I propose adding such a property to layers. For example, it can be name, UUID, ID etc.