aboutsummaryrefslogtreecommitdiffstats
path: root/reference/logging-slf4j/README.md
diff options
context:
space:
mode:
authorLuke Parker <lparker@amdocs.com>2018-06-19 23:35:33 +1000
committerLuke Parker <lparker@amdocs.com>2018-06-19 23:35:33 +1000
commitbca830c8ee8cc574bd3f05e0599c56d05ba011e2 (patch)
treecbc2de21009e88e0e852b1baad56c8cf972e683e /reference/logging-slf4j/README.md
parentf78f68dc817cbbf76f2d65e68c955f0ec3e65d2d (diff)
Change MDC datetime formatter to Zulu time
Change-Id: I0e771e0ec10d1972290c44e8e0740309ac83bc52 Signed-off-by: Luke Parker <lparker@amdocs.com> Issue-ID: LOG-115
Diffstat (limited to 'reference/logging-slf4j/README.md')
-rw-r--r--reference/logging-slf4j/README.md23
1 files changed, 5 insertions, 18 deletions
diff --git a/reference/logging-slf4j/README.md b/reference/logging-slf4j/README.md
index 2796a21..bbad3b3 100644
--- a/reference/logging-slf4j/README.md
+++ b/reference/logging-slf4j/README.md
@@ -25,26 +25,13 @@ The adapter provides:
Note that:
* The adapter implementation uses static inner classes in order to fit in a single source file. This was an objective.
-## WAR
-
-Building produces a simple (spring-boot](https://projects.spring.io/spring-boot/) example WAR, which can be launched from this directory with:
-
-```bash
-$ java -war target/*war
-```
-
-The example WAR in ```logging-slf4j-demo``` publishes four web services:
-1. ```services/alpha```
-2. ```services/beta```
-3. ```services/gamma```
-4. ```services/delta```
+The purpose of the WAR is to demonstrate minimalist ONAP-compliant logging for web components, but a secondary purpose is to demonstrate that the call graph can be generated for a (mostly) representative set of interacting REST services.
-... each of which can invoke the others.
+## Configuration
-The purpose of the WAR is to demonstrate minimalist ONAP-compliant logging for web components, but a secondary purpose is to demonstrate that the call graph can be generated for a (mostly) representative set of interacting REST services.
+Note that the bundled SLF4J configuration *isn't* meant to be normative. Close enough as makes no difference for
+the purposes of tests, but be aware that it might not always be up-to-date.
## Tests
-Tests for:
-1. Code in the (potentially) reusable ``common`` package.
-2. Validating that emitted logs can be used to generate an unambiguous call graph.
+TestNG tests for contract + output of SLF4J reference impl.