Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+r7YvkwbQt50CCaPvm38eekMT6vioTXpPzgnpf-FrXQ6B9a2w@mail.gmail.com>
References: 
 <CA+r7YvkwbQt50CCaPvm38eekMT6vioTXpPzgnpf-FrXQ6B9a2w@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 24 Sep 2015 16:04:37 +0200
Message-ID: 
 <CAGB5yNnNN_9xHC3y=SytUPQz0t+6mq6r72myQj-XMi_3JE+5GA@mail.gmail.com>
Subject: Re: Sending stats back to Jetty after split
To: dev <dev@camel.apache.org>
Content-Type: text/plain; charset=UTF-8

The splitter supports an aggregation strategy where you can build a
repsonse object with the splitted messages.

See splitter only example on
http://camel.apache.org/composed-message-processor.html

On Thu, Sep 24, 2015 at 3:59 PM, Asaf Mesika <asaf.mesika@gmail.com> wrote:
> Hi,
>
> I have a Jetty end-point which I consume (hope I'm getting the right
> terminology, still I'm still learning this) - meaning it's acting as a
> server accepting a POST request containing lines separated by a new-line.
>
> I then have a streaming splitter based on new line, and then a parse-json
> processor which parses the line as JSON. After that I'm sending it to a
> direct end-point (which is another route).
>
> I would like to send back stats as a response, including the number of
> lines which failed parsing.
>
> I couldn't find a way to to relay this stats from the parse-json processor
> back to the original exchange which left the Jetty end-point.
> Any idea?
>
>
> Question 2:
>
> I would like to extend the splitter to have a max line length, thus if
> someone send 10 lines, but the 3rd is 2 mb long, then it will gracefully
> skipped.
> Does it exists some where other than the main camel repo?
>
> If I would like to commit this feature back, what is the exact process I
> should follow?
>
> Thanks!
>
> Asaf


-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition: https://www.manning.com/books/ibsen2