-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
simulator run modes: [async/sync] #241
Conversation
9b125b2
to
7da5a64
Compare
@novarx interested in your opinion! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - missing some tests 😉
.../main/java/org/citrusframework/simulator/service/runner/SyncScenarioExecutorServiceImpl.java
Outdated
Show resolved
Hide resolved
yeah, didn't even know if this proves usable.. so, didn't bother. |
2403382
to
e1c40ea
Compare
...test/java/org/citrusframework/simulator/service/runner/DefaultScenarioExecutorServiceIT.java
Show resolved
Hide resolved
...test/java/org/citrusframework/simulator/service/runner/DefaultScenarioExecutorServiceIT.java
Outdated
Show resolved
Hide resolved
...rc/test/java/org/citrusframework/simulator/service/runner/SyncScenarioExecutorServiceIT.java
Outdated
Show resolved
Hide resolved
...lator-spring-boot/src/main/java/org/citrusframework/simulator/web/rest/ScenarioResource.java
Show resolved
Hide resolved
...pring-boot/src/main/java/org/citrusframework/simulator/listener/SimulatorStatusListener.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/citrusframework/simulator/service/runner/AsyncScenarioExecutorService.java
Outdated
Show resolved
Hide resolved
...c/main/java/org/citrusframework/simulator/service/runner/DefaultScenarioExecutorService.java
Show resolved
Hide resolved
e1c40ea
to
940704a
Compare
@christophd are you ok with this change? 🥇 |
940704a
to
0bbc987
Compare
note that we've beta tested this internally and fixed another two bugs in the process. I must sign this commits of tonight, before merging. |
Signed-off-by: Timon Borter <timon.borter@gmx.ch>
the property `citrus.simulator.mode=[async/sync]` steers the mode the simulator will use to execute simulations. note that while the synchronous modus is simpler, it disallows the simulation of any intermediate messaging with synchronous protocols. Signed-off-by: Timon Borter <timon.borter@gmx.ch>
Signed-off-by: Timon Borter <timon.borter@gmx.ch>
Signed-off-by: Timon Borter <timon.borter@gmx.ch>
Signed-off-by: Timon Borter <timon.borter@gmx.ch>
0bbc987
to
0c23ed5
Compare
add "run modes" to the simulator:
sync
allows only request-response simulations, because there is no additional threadasync
allows intermediate messaging, if that is requried, uses an additional thread pool for simulations