Changed remaining StubTrigger interface name

This commit is contained in:
Marcin Grzejszczak
2016-04-25 15:47:23 +02:00
parent 3232adefe6
commit 50dc90df76
4 changed files with 4 additions and 4 deletions

View File

@@ -12,7 +12,7 @@ It also provides points of entry to integrate with any other solution on the mar
=== Stub triggering
To trigger a message it's enough to use the `StubTiggerer` interface:
To trigger a message it's enough to use the `StubTigger` interface:
[source,groovy]
----

View File

@@ -69,7 +69,7 @@ include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/camel/CamelSt
===== Scenario 1 (no input message)
So as to trigger a message via the `return_book_1` label we'll use the `StubTiggerer` interface as follows
So as to trigger a message via the `return_book_1` label we'll use the `StubTigger` interface as follows
[source,groovy]
----

View File

@@ -77,7 +77,7 @@ include::src/test/resources/integration-context.xml[]
===== Scenario 1 (no input message)
So as to trigger a message via the `return_book_1` label we'll use the `StubTiggerer` interface as follows
So as to trigger a message via the `return_book_1` label we'll use the `StubTigger` interface as follows
[source,groovy]
----

View File

@@ -69,7 +69,7 @@ include::src/test/groovy/io/codearte/accurest/stubrunner/messaging/stream/Stream
===== Scenario 1 (no input message)
So as to trigger a message via the `return_book_1` label we'll use the `StubTiggerer` interface as follows
So as to trigger a message via the `return_book_1` label we'll use the `StubTigger` interface as follows
[source,groovy]
----