Hi,
It sounds like Camel would definitely be good fit for the scenario you are
describing. It's the kind of integration problem that Camel is meant for!
You may be able to leverage some features of your JMS provider (have you
decided on one?) for the TTL since JMS messages can have a property for
expiration. It sounds like your recipients are actually subscribers to a
topic. In that case, it should be easier if your JMS provider offers durable
subscriptions so that your recipients can get non-expired messages when they
are back on line.
I think ServiceMix and Camel are products that work well together and that
address different needs. I have been using Camel for over a year and have
been very satisfied. It's a huge productivity enabler when it comes to
integration problems and it's fun to use. :)
Good luck,Mathieu.
> Date: Sun, 28 Aug 2011 18:13:07 +0400
> Subject: How much mule suits for split with TTL?
> From: vitaliy...@gmail.com
> To: users@camel.apache.org
>
> Hello,
>
> i'm new to Camel and at the moment choosing between Mule, Apache
> ServiceMix or Apache Camel for solving following task:
>
> A flow starts when web service is called , N recipients ( a folder
> with files, web service, jms queue) receive the message
> Monitoring (at least logging) is needed.
> Multiple similar flows can exists.
> In case a recipient is offline the flow should wait till it gets
> online or report failure if TTL is exceeded.
> Online redeployment is needed. During redeployment of a flow the
> flows that are running are not stopped. (optional)
>
>
> Would be grateful if people with experience will give a hits if Camel
> suits for such tasks and how would it be better to implement it, or
> maybe Mule or ServiceMix suits for it better?
>
> Thanks in advance,
> Vitaly
