The next step in the route may not be an endpoint, so it's not
"addressable" in that way.
On Mon, Oct 7, 2013 at 12:02 PM, Chris wrote:
> James, thanks for the suggestion - I'll try that, however, I would still
> like to know if/how a given endpoint can programmtically find the next
> down-stream
James, thanks for the suggestion - I'll try that, however, I would still
like to know if/how a given endpoint can programmtically find the next
down-stream endpoint in a route...
On 10/4/2013 1:38 PM, James Carman wrote:
Does a splitter not work for you in this case?
On Fri, Oct 4, 2013 at 1:
Does a splitter not work for you in this case?
On Fri, Oct 4, 2013 at 1:28 PM, Chris wrote:
> Hello,
>
> I implemented a bean whose method accepts an exchange with a single message,
> then generates multiple messages intended for the next endpoint down-stream,
> along the lines of this:
>
> http:
