Testing InOut route with a <to> in the middle...

[catlinit]

I have a problem testing a route.   Its Spring wired in its own xml file with the actuals endpoints wired in another xml file and accessed through vm endpoints. The route is something like:

          ... etc the response I'm looking for...";

    @Test

    public void shouldExcersiseRoute() throws Exception {

        mockSearchEndpoint.whenAnyExchangeReceived(

                new Processor() {

                    @Override

                    public void process(Exchange exchange) {

                        exchange.getOut().setBody(new ByteArrayInputStream(resp

                                .getBytes()));

                    }

                });

        Object body = new MessageContentsList(new DOMSource(getDocument(msg)));

        Object response = template.requestBody(body);

        assertEquals("...Assert the response is found...", response);

    }

    private Document getDocument(String xml) throws Exception {

        DocumentBuilderFactory factory =

                DocumentBuilderFactory.newInstance();

        factory.setNamespaceAware(true);

        InputSource source = new InputSource(new StringReader(xml));

        DocumentBuilder docBuilder = factory.newDocumentBuilder();

        Document doc = docBuilder.parse(source);

        return doc;

    }

I can see when debugging that the processor for the vm:restQuery is called but I never get a response from the .requestBody with the test eventually timing out.

How does one go about testing a route where it interacts with other end points before sending the response?   Is my approach correct but I'm missing something on the interaction with vm:restQuery?

Thanks

[njiang]

As you doesn't setup the route of mock://vm:restQuery, you may consider to add the route like this into your camel context before running the test.

    from("vm:restQuery").to("mock://vm:restQuery");

Or you can use the interceptSendToEndpoint() DSL to simulate the response from the processor. You can find more example in the Camel in Action Chapter6.

Willem

[catlinit]

Thanks.  The solution was to remove any reference and use of mocks and use the interceptSendToEndpoint on the vm:restQuery endpoint to return the value.