Hi,
Your route looks weird to me.
What's the direct:start trigger ?
What do you do with the reply ?
For instance, a valid testing route would be:
from("timer:foo?period=5000").to("...").log("Received ${body}")
Or at least expose an endpoint as a bridge (as we do in the Karaf example).
Regards
Hi Jean and Francois,
Thanks for the reply :)
I have already seen the examples and successfully execute the one given in
/apache-karaf/examples/karaf-camel-example/karaf-camel-example-java
directory.
But when I'm trying to put my own camel code, I'm not able to call the
route endpoint.
For eg.
Thanks a lot, Claus :)
On Sun, Oct 6, 2019 at 3:07 PM Claus Ibsen wrote:
> Hi
>
> What json-simple are you referring to?
>
> You can see the list of features with features:list
>
> And you can use --help to see command line help, as I think it has
> parameters to filter the list, or pipe to grep
Can anyone point me to working example of spring.liquibase.enabled=false
The Camel community announces the immediate availability of Camel
3.0.0-RC2, the second release candidate towards a new 3.0.0 major
release with 94 improvements and fixes.
The artifacts are published and ready for you to download from the
Central Maven repository. For more details please take a lo
Hi,
I am using netty TCP to receive bytes. If the message size is big, its
getting read in chunks, can you please suggest how to avoid this. I want to
be able to read the entire message. I was sending a message of 32KB. I see
that the first 1024bytes were read and the flow proceeded to the next
pro
Hi
What json-simple are you referring to?
You can see the list of features with features:list
And you can use --help to see command line help, as I think it has
parameters to filter the list, or pipe to grep
features:list | grep camel
On Sat, Oct 5, 2019 at 5:26 PM Jaiprakash Mewada
wrote:
>
