It is not a typo. We may be missing documentation. I’ll have to search and see.
Ralph > On Dec 20, 2021, at 1:18 PM, Gary Gregory <[email protected]> wrote: > > Our page > https://logging.apache.org/log4j/2.x/manual/configuration.html#SystemProperties > documents log4j2.component.properties, but you talk about > log4j2.system.properties. Is that a typo or are we missing > documentation? > > Gary > > On Mon, Dec 20, 2021 at 3:12 PM Ralph Goers <[email protected]> > wrote: >> >> This proposal is problematic. By the time this happens it is possible it is >> too late for some system properties to do any good. >> >> I implemented support for system properties already. I had a need for it for >> the Spring support. Just put the properties in log4j2.system.properties. >> >> PropertiesUtil populates the SystemProperties when it creates the >> Environment. >> >> Ralph >> >>> On Dec 20, 2021, at 12:18 PM, Gary Gregory <[email protected]> wrote: >>> >>> Hello, >>> >>> I'd like to propose that we add an element called SystemProperty to >>> our configuration. This would look like our current Property element >>> but would set a system property instead of a configuration property. >>> >>> My use case is, at work, our tooling generates one XML configuration >>> file for a user's project and additional XML files for each DTAP >>> environment. The main Log4j configuration file uses XInclude to bring >>> in the appropriate DTAP file. Depending on the configuration of the >>> user's project, and in light of Log4j's use of system properties, >>> specifically, our new enableJndi* system properties, it would be nice >>> to be able to say in DTAP XML files something like <SystemProperty >>> key="enableJndiJms>true</SystemProperty> or whatever Property >>> supports. >>> >>> Thoughts? >>> >>> Gary >>> >> >
