See these EIPs
http://camel.apache.org/content-enricher.html
http://camel.apache.org/composed-message-processor.html
And the latter has the splitter only mode
On Thu, Jul 23, 2015 at 8:58 PM, vivekrao001 wrote:
> Putting the first result in the header is the only way?
>
>
>
> --
> View this mess
Putting the first result in the header is the only way?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Concatenating-input-and-output-for-an-endpoint-tp5769829p5769845.html
Sent from the Camel - Users mailing list archive at Nabble.com.
You must be doing some more inside the splitter and you may need 2 x end
On Thu, Jul 23, 2015 at 7:45 PM, Wilson MacGyver wrote:
> hmm, if I understand you correctly, this isn't working for me.
>
> I have
>
> from()
>
> .split(body().tokenize("\n")).streaming()
>
> .process() /do stuff
>
> .end()
from("direct:readsql").to("sql:select * from orders where processed =
false").split(body())
.parallelProcessing().to("direct:split");
from("direct:split").to("sql:select * from orders_address where id=
:#${body[ID]}").log("Message :${body}");
Is there a way to conca
hmm, if I understand you correctly, this isn't working for me.
I have
from()
.split(body().tokenize("\n")).streaming()
.process() /do stuff
.end()
.log("${in.body}")
.to(smtp://)
say if the file has 100 lines, I'd except to see the log once if I
understand what you are saying correctly. bu
Yeah always above until its fixed etc.
On Thu, Jul 23, 2015 at 2:19 PM, Ryan Moquin wrote:
> Does this affect only 2.13.0? Just confirming since that's the only
> version mentioned in the ticket but guessing it affects 2.13.0 and above?
>
> On Thu, Jul 23, 2015, 1:58 AM Claus Ibsen wrote:
>
>>
You can do that after the splitter
... inside splitter
.. split done
send email here
In Java DSL you can use .end() to end the split block.
On Thu, Jul 23, 2015 at 7:21 PM, Wilson MacGyver wrote:
> Hi,
>
> I'm processing a large file. so I use .split and .streaming to process it
Hi,
I'm processing a large file. so I use .split and .streaming to process it a
record at a time.
I would like to send an email alert upon completion of processing the file.
but I can't figure out where to do that.
I know I can check to see if it's the last exchange using property
"CamelSplitCo
As I understand it, if you have an exception handler then the dead letter
processing should not get invoked.
However, according to the tests below if you do not have some kind of
processor in the exception handler, the dead letter logic does in fact get
invoked.
Is this behavior by design? It is ce
Hi,
@Claus: Thanks a lot for your help.
Found a configuration that works, for the record, here it is:
The JmsComponent must not have "lazy-init=true", because Camel expects the
bean to be there to initialize the route. But with "lookupOnStartup =false"
in the JndiObjectFactoryBean, the JMSConnec
> On Jul 22, 2015, at 2:39 PM, Ed Welch wrote:
>
> Hi Achim!
>
> I set out on that path this morning, but it looks like the camel-cxf feature
> in camel 2.15.2 has a dependency or a dependent feature with an upper bound
> which won't accept jetty 9:
>
> Error executing command: Unable to res
Does this affect only 2.13.0? Just confirming since that's the only
version mentioned in the ticket but guessing it affects 2.13.0 and above?
On Thu, Jul 23, 2015, 1:58 AM Claus Ibsen wrote:
> Hi
>
> I think we have a ticket about this
> https://issues.apache.org/jira/browse/CAMEL-6707
>
> You
Hello
Sorry for the delay - please check how this is done in
http://camel.apache.org/jetty.html
regards
Grzegorz
2015-07-11 4:35 GMT+02:00 mayur_bm :
> Thanks Grzybek,
>
> in case if i use the approach given here
> http://rrusin.blogspot.in/2010/07/jetty-webapp-osgi-way.html , will i be
> consu
13 matches
Mail list logo
