I'd really recommend using VTD or something similar to split large XML. Much
faster and more memory efficient.
Define a bean that does the split and returns an iterator and supply it as
the method for split.
Simple example using VTD to split XML:
http://stackoverflow.com/questions/1640472/java-ho
I have a route setup that looks like this:
It's purpose is to run once at startup to get an intial value (in this
example I just have sending to out instead of doing anything with the reply)
and never run again.
The shutdownRequestor bean has a handler that looks like this:
public
Title is a little weird as I didn't quite know the proper way to phrase this.
I'm interested in logging the duration of certain things, such as how long
it takes the file component to read or write a file, how long it takes the
jms component to publish or consume a message, etc.
As an example, my
itiques or suggestions for how I could
improve things further are very welcome.
Thanks,
Jason
Claus Ibsen-2 wrote:
>
> On Thu, Apr 30, 2009 at 10:13 PM, jburkhardt
> wrote:
>>
>> I've looked around JIRA and it seems using stop in spring dsl used to be
>> an
&
te:
>
> Have you tried to put that processor as a filter before the split?
>
>
>
> Em 30/04/2009 17:13, jburkhardt escreveu:
>
>
>> I've looked around JIRA and it seems using stop in spring dsl used to be
>> an
>
>> issue but has been resolved sin
I've looked around JIRA and it seems using stop in spring dsl used to be an
issue but has been resolved since Feb 09. Perhaps I am attempting to use it
incorrectly.
I am using Camel 2.0 M1
Here's what I'm trying to do:
I have a route that receives messages from a JMS queue.
After receiving the m