Re: Log4j2 - combining .properties and .xml config files
Ralph Goers <[email protected]> Mon, 6 Aug 2018 06:25:47 -0700
| Newsgroups | gmane.comp.apache.logging,gmane.comp.jakarta.log4j.devel,gmane.comp.jakarta.log4j.user |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail=_340F4844-A696-4870-9CBD-CB775747F086 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 You can do this today. See = http://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeCon= figuration = <http://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeCo= nfiguration>. > On Aug 6, 2018, at 5:55 AM, Fr=C3=B6stl, Christian = <[email protected]> wrote: >=20 > Hi everybody, >=20 > I just wanted to know if it is planned to combine different logging = configuration in the future, or if it is still possible today? >=20 > Example: > - Base logging configuration is a log4j2.xml from the classpath > - Logging could be extended by adding new loggers to the .properties = files >=20 > Could this be a valid case in the future of log4j2 or is there a = strict separation between .properties and .xml files? (or even = properties and JSON files) >=20 > Thanks and greetings, > Christian >=20 >=20 > ________________________________ >=20 > This message is for the designated recipient only and may contain = privileged, proprietary, or otherwise confidential information. If you = have received it in error, please notify the sender immediately and = delete the original. Any other use of the e-mail by you is prohibited. = Where allowed by local law, electronic communications with Accenture and = its affiliates, including e-mail and instant messaging (including = content), may be scanned by our systems for the purposes of information = security and assessment of internal compliance with Accenture policy. = Your privacy is important to us. Accenture uses your personal data only = in compliance with data protection laws. For further information on how = Accenture processes your personal data, please see our privacy statement = at https://www.accenture.com/us-en/privacy-policy. > = __________________________________________________________________________= ____________ >=20 > www.accenture.com >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >=20 --Apple-Mail=_340F4844-A696-4870-9CBD-CB775747F086 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">You = can do this today. See <a = href=3D"http://logging.apache.org/log4j/2.x/manual/configuration.html#Comp= ositeConfiguration" = class=3D"">http://logging.apache.org/log4j/2.x/manual/configuration.html#C= ompositeConfiguration</a>.<br class=3D""><div><br class=3D""><blockquote = type=3D"cite" class=3D""><div class=3D"">On Aug 6, 2018, at 5:55 AM, = Fr=C3=B6stl, Christian <<a = href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Hi = everybody,<br class=3D""><br class=3D"">I just wanted to know if it is = planned to combine different logging configuration in the future, or if = it is still possible today?<br class=3D""><br class=3D"">Example:<br = class=3D"">- Base logging configuration is a log4j2.xml from the = classpath<br class=3D"">- Logging could be extended by adding new = loggers to the .properties files<br class=3D""><br class=3D"">Could this = be a valid case in the future of log4j2 or is there a strict separation = between .properties and .xml files? (or even properties and JSON = files)<br class=3D""><br class=3D"">Thanks and greetings,<br = class=3D"">Christian<br class=3D""><br class=3D""><br = class=3D"">________________________________<br class=3D""><br = class=3D"">This message is for the designated recipient only and may = contain privileged, proprietary, or otherwise confidential information. = If you have received it in error, please notify the sender immediately = and delete the original. Any other use of the e-mail by you is = prohibited. Where allowed by local law, electronic communications with = Accenture and its affiliates, including e-mail and instant messaging = (including content), may be scanned by our systems for the purposes of = information security and assessment of internal compliance with = Accenture policy. Your privacy is important to us. Accenture uses your = personal data only in compliance with data protection laws. For further = information on how Accenture processes your personal data, please see = our privacy statement at <a = href=3D"https://www.accenture.com/us-en/privacy-policy" = class=3D"">https://www.accenture.com/us-en/privacy-policy</a>.<br = class=3D"">_______________________________________________________________= _______________________<br class=3D""><br class=3D""><a = href=3D"http://www.accenture.com" class=3D"">www.accenture.com</a><br = class=3D""><br = class=3D"">---------------------------------------------------------------= ------<br class=3D"">To unsubscribe, e-mail: = [email protected]<br class=3D"">For additional = commands, e-mail: [email protected]<br class=3D""><br = class=3D""></div></div></blockquote></div><br class=3D""></body></html>= --Apple-Mail=_340F4844-A696-4870-9CBD-CB775747F086--