rom("jetty:http://0.0.0.0:8081/hello";)
.to("mongodb:myDb?database=test&collection=test&operation=insert")
.log("${body}")
.setBody(simple("${body}"))
;
}
}
David Yang
Computer Science
Thanks for the responses. We looked through the materials but they didn't
quite solve our problem. What we want to do is use Camel's FtpConsumer for a
one time shot:
1. Check a ftp site
2. Process all the files
3. Shut down after processing (the entire JVM etc).
I thought one path we coul
Thanks for the response Richard - was very helpful.
Any sense of how large exchange message bodies can get? Should we use that
itself as the transfer mechanism or have some other form of transport?
I'm also curious if we want to reuse a bunch of these components we're creating
across various
We're still getting to know Camel but one of the things we'd like to try is to
have a step in our pipeline where HTML data (or a file location) is passed to
firefox and converted to PDF. We'd like to probably pass a location on disk or
perhaps just the entire HTML as data.
How should we go ab
I'm curious how others are solving the problem of managing configuration across
various routes, components etc inside a Camel Context.
We've written some Components that themselves need to have connections to
various DB's etc. If we want to have a development and production properties
for eac
