--
You received this message because you are subscribed to the Google Groups "ESAPI Project Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to esapi-project-...@owasp.org.
To view this discussion on the web visit https://groups.google.com/a/owasp.org/d/msgid/esapi-project-dev/9796bc24-c871-4d6b-914e-784c287a01a5n%40owasp.org.
- A high-level explanation of what value is added to a system through the ESAPI Logging support classes.
- A breakout of the applicable values in ESAPI.properties, and samples of how the system output should be impacted. This relates to the note of 2.2.1.0 above.
- To support the use of either Log4J2 or Logback implementation I was going to also add links to the maven central download locations for each of the resources so readers may reference the 'latest available' versions of those support libraries.
- I had also considered adding links to the documentation on logging configuration for each Logback and SLF4J.
- Configuration Samples? The basic logging support for both Log4J2 and Logback are fairly small. It may be possible to stub the configurations we have in this document, and refer to the configuration directory for the latest released support content. I hadn't thought this through very much, but had a note for consideration.
- A reference to the Null Implementation (no-op) logging dependency to support local testing efforts may (or may not) be of value to some users. Benefit here is that in testing they can focus on their output and not ours, and do not see SLF4J warnings in the output. This should be clearly identified as something that should be exclusively for test-scope declarations. (this is just a declared test-scope dependency)