From 8a5c5d9787448241d34a5a525a87d02add55949b Mon Sep 17 00:00:00 2001 From: xstefank Date: Mon, 15 Jul 2019 22:17:34 +0200 Subject: [PATCH] Fix specification wording with regards to deployment phase Signed-off-by: xstefank --- spec/src/main/asciidoc/microprofile-lra-spec.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/src/main/asciidoc/microprofile-lra-spec.adoc b/spec/src/main/asciidoc/microprofile-lra-spec.adoc index 13c9228e..4d94a2d9 100644 --- a/spec/src/main/asciidoc/microprofile-lra-spec.adoc +++ b/spec/src/main/asciidoc/microprofile-lra-spec.adoc @@ -809,7 +809,7 @@ A method annotated with `@AfterLRA` that is not a JAX-RS resource method MUST ac two arguments of type URI and LRAStatus, in that order. The first parameter holds an LRA context and the second parameter holds the final status of the LRA. If the signature does not conform to this requirement then the implementation MUST -prohibit the successful startup of the application (e.g. through the deployment time +prohibit the successful startup of the application (e.g. through the startup time runtime exception). An example of a valid signature is: @@ -841,7 +841,7 @@ defined types Declaring more than two arguments, different types of arguments or different return type for any non-JAX-RS method annotatated with the participant marker annotation MUST result -in the prohibition of the successful application startup (e.g. through the deployment +in the prohibition of the successful application startup (e.g. through the startup time runtime exception). Please note that both arguments are optional but the order is required. This means that