From b82f697bb6ee364eb80b0ab5da0c2626ef94c50a Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Sun, 24 Apr 2016 18:24:09 +0200 Subject: [PATCH] Updated docs --- .../README.adoc | 29 ++----------------- .../stub-runner-messaging-stream/README.adoc | 29 ++----------------- 2 files changed, 6 insertions(+), 52 deletions(-) diff --git a/stub-runner/stub-runner-messaging/stub-runner-messaging-integration/README.adoc b/stub-runner/stub-runner-messaging/stub-runner-messaging-integration/README.adoc index 8e87674940..0e935fe739 100644 --- a/stub-runner/stub-runner-messaging/stub-runner-messaging-integration/README.adoc +++ b/stub-runner/stub-runner-messaging/stub-runner-messaging-integration/README.adoc @@ -121,34 +121,11 @@ And the received message would pass the following assertions include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/integration/IntegrationStubRunnerSpec.groovy[tags=client_receive_message,indent=0] ---- -===== Custom triggers +===== Scenario 3 (input with no output) -`StubTrigger` gives you the following options to trigger a message: - -===== Trigger by label +Since the route is set for you it's enough to just send a message to the `{input_name}` destination. [source,groovy] ---- -include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/integration/IntegrationStubRunnerSpec.groovy[tags=client_trigger,indent=0] +include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/integration/IntegrationStubRunnerSpec.groovy[tags=trigger_no_output,indent=0] ---- - -===== Trigger by group and artifact ids - -[source,groovy] ----- -include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/integration/IntegrationStubRunnerSpec.groovy[tags=trigger_group_artifact,indent=0] ----- - -===== Trigger by artifact ids - -[source,groovy] ----- -include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/integration/IntegrationStubRunnerSpec.groovy[tags=trigger_artifact,indent=0] ----- - -===== Trigger all messages - -[source,groovy] ----- -include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/integration/IntegrationStubRunnerSpec.groovy[tags=trigger_all,indent=0] ----- \ No newline at end of file diff --git a/stub-runner/stub-runner-messaging/stub-runner-messaging-stream/README.adoc b/stub-runner/stub-runner-messaging/stub-runner-messaging-stream/README.adoc index 6936bef94e..cda8a5a32b 100644 --- a/stub-runner/stub-runner-messaging/stub-runner-messaging-stream/README.adoc +++ b/stub-runner/stub-runner-messaging/stub-runner-messaging-stream/README.adoc @@ -113,34 +113,11 @@ And the received message would pass the following assertions include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/stream/StreamStubRunnerSpec.groovy[tags=client_receive_message,indent=0] ---- -===== Custom triggers +===== Scenario 3 (input with no output) -`StubTrigger` gives you the following options to trigger a message: - -===== Trigger by label +Since the route is set for you it's enough to just send a message to the `{output_name}` destination. [source,groovy] ---- -include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/stream/StreamStubRunnerSpec.groovy[tags=client_trigger,indent=0] +include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/stream/StreamStubRunnerSpec.groovy[tags=trigger_no_output,indent=0] ---- - -===== Trigger by group and artifact ids - -[source,groovy] ----- -include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/stream/StreamStubRunnerSpec.groovy[tags=trigger_group_artifact,indent=0] ----- - -===== Trigger by artifact ids - -[source,groovy] ----- -include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/stream/StreamStubRunnerSpec.groovy[tags=trigger_artifact,indent=0] ----- - -===== Trigger all messages - -[source,groovy] ----- -include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/stream/StreamStubRunnerSpec.groovy[tags=trigger_all,indent=0] ----- \ No newline at end of file