Minh - that's exactly what I'm trying to do. The issue is that I don't have
a great hook to insert my advice where I want.
Claus - here's a rough example:
from("direct:start")
.setBody().constant(someXml)
.split().xpath(anXpathExpression)
.setHeader("myHeader", constant(somethingObtainedFromXpath))
.to("mock:polluted")
.split().xpath(anotherXpath)
.to("seda:result");
Let's say that I wanted to write some tests that ensured that the first
xpath gave me what I wanted. I could just do what I've shown above and
throw a mock endpoint in there that I can use as an adviceWith
interceptSendTo hook, but I'm wondering if there's a better alternative
than that.
Jeff
On Fri, Apr 22, 2016 at 6:58 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> On Thu, Apr 21, 2016 at 8:18 PM, Jeff Segal <jeffrey.se...@gmail.com>
> wrote:
> > I've got a route that I'd like to do some unit testing on at various
> > stages. It does a few splits, sets some headers, etc. The problem is that
> > there's no actual endpoint for me to intercept until the very end, but
> I'd
> > like to do some verification midway through.
> >
> > I suppose I could add arbitrary mock endpoints in key spots to use as
> > interceptSendTo hooks, but I'd rather not pollute my route with test
> > scaffolding like that. I've also tried using vanilla intercept().when()
> > calls but those end up casting too wide a net to be useful (or don't
> offer
> > a straightforward way for to intercept where and only where I want to).
> >
> > Is there a better alternative to solving this problem than injecting
> > arbitrary mocks into my production routes?
> >
>
> Can you provide an example. I think that would help understand what you
> explain.
>
>
> > Jeff
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
