Gateway sounds to me like a way to test a service itself, not the whole orchestration, am I right?
Anyway thanks Mark and Oleg, it's very refreshing to see your quick and good replies.
Printable View
Gateway sounds to me like a way to test a service itself, not the whole orchestration, am I right?
Anyway thanks Mark and Oleg, it's very refreshing to see your quick and good replies.
Not necessarily. I guess I am missing exactly what you are trying to do, so may be you can explain.
You can also go through our extensive library of samples https://github.com/SpringSource/spri...ration-samples where Gateway is used in many of them. May be that will answer some of your questions.
There is an abstract class in spring-integration-test (2.1.RC1) that does (I think) exactly what you want - it abstracts the channel type and you provide a handler, regardless. SeeQuote:
...But I do feel that this kind of test tools, even if they don't reside in the core, are quite needed,
You extend this class - there are some examples of how to use it in src/test/java in that project. See MessageScenariosTests.Code:/**
* Convenience class for testing Spring Integration request-response message scenarios. Users
* create subclasses to execute on or more {@link RequestResponseScenario} tests. each scenario defines:
* <ul>
* <li>An inputChannelName</li>
* <li>An outputChannelName</li>
* <li>A payload or message to send as a request message on the inputChannel</li>
* <li>A handler to validate the response received on the outputChannel</li>
* </ul>
* @author David Turanski
*/
@RunWith(SpringJUnit4ClassRunner.class)
public abstract class AbstractRequestResponseScenarioTests {
HTH
Gary thats great!
That's exactly what I was looking for, thank you very much to all of you.