#x27;s
jms support than any other option mentioned.
On Wed, Jul 18, 2012 at 10:45 AM, Sam (Stephen Samuel) wrote:
> I'll stick with JMS then, didn't know if Camel had some kind of
> Hazelcast type thing.
>
> On Wed, Jul 18, 2012 at 3:39 PM, thomas barker
> wrote:
> &g
If you use JMS use activemq if you can... the http / servlet / jetty
components are lightweight options as well.
On Wed, Jul 18, 2012 at 10:36 AM, Charles wrote:
> 1.) Use JMS
> 2.) Use CXF (web services)
>
> I've done #1, it's probably easier.
>
>
> - Original Message -
> From: Sam (Ste
I much prefer java dsl for maintainability. Spring DSL is fine for small,
simple routes that will never grow. As a response to the previous, I am
not sure I would use Camel if maintenance was done by non-devs.
On Fri, Jul 6, 2012 at 11:35 AM, Sam (Stephen Samuel)
wrote:
> IMO
>
> Pro Spring:
>
bean or
pollenrich. I originally wrote this code to deal with sftp, but I use it
for file as well.
If you want the code I am happy to find it at some point.
On Mon, Jul 2, 2012 at 10:28 AM, thomas barker wrote:
> I have done this before, it may take me a bit to find the code. I thi
I have done this before, it may take me a bit to find the code. I think
you accomplish it by doing the following:
1. Override the from(String) method in RouteBuilder
2. Use getContext().getEndpoint(uri) to get the endpoint, if the endpoint
is not a scheduledpollingendpoint then do super.from(ur
