From 976e1cb530da0c306f0fbb1b103ed110689de9de Mon Sep 17 00:00:00 2001 From: Nathan Rauh Date: Mon, 13 Jul 2020 14:32:30 -0500 Subject: [PATCH] Issue #193 address code review comment about mp config example --- README.adoc | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/README.adoc b/README.adoc index 62dabe8..0a02bb8 100644 --- a/README.adoc +++ b/README.adoc @@ -177,17 +177,15 @@ by implementations that are also Jakarta/Java EE application servers. // TODO: insert links to implementation defaults here, once available -Applications can achieve portability across implementations with respect to propagated -context types either by explicitly specifying the context propagation on the builder -or by explicitly configuring the desired defaults via MicroProfile Config properties. +You can define your own defaults for context propagation via MicroProfile Config properties. For example, [source,java] ---- -mp.context.ManagedExecutor.propagated=Application,CDI,Security -mp.context.ManagedExecutor.cleared=Remaining -mp.context.ThreadContext.propagated=Application,CDI,Security -mp.context.ThreadContext.cleared=Remaining +mp.context.ManagedExecutor.cleared=Transaction +mp.context.ManagedExecutor.propagated=Remaining +mp.context.ThreadContext.cleared=Transaction +mp.context.ThreadContext.propagated=Remaining ---- [[spi-for-context-providers]]