Re: [DISCUSS] Message Store

2012-10-23 Thread Bengt Rodehav
I think this is an excellent idea. We're using Camel as the basis for our integration platform and a message store is a mandatory component. We need: - To store all message traffic in order to have an audit trail. Both successful and failed exchanges. - To provide a certain level of manual retry.

Re: [DISCUSS] Message Store

2012-10-23 Thread Willem jiang
There is a lots of way to implement to Message store. Option1. If we treat is a first class of Camel, we could build up a set of API to let aggregator or tracer to use. As it is common usage that we need to store the exchange persistently, It make sense to provides such kind of API in Camel as

Re: [DISCUSS] Message Store

2012-10-23 Thread Hadrian Zbarcea
Hi Christian, You are correct about the fact that a Message Store is missing (kinda). There are a few components that support a message store implementation of sorts, as you mentioned. You are also correct that it should be a first class citizen. Practically, an endpoint that supports a poll

RE: Camel cold restart via JMX

2012-10-23 Thread Daniel Gredler
Hi Willem, That was fast :-) Thanks a ton; hopefully it'll be useful to others, as well. Take care, Daniel -Original Message- From: Willem jiang [mailto:willem.ji...@gmail.com] Sent: Monday, October 22, 2012 11:52 PM To: dev@camel.apache.org Subject: Re: Camel cold restart via JMX H

Re: adding Bindings to Endpoints...

2012-10-23 Thread James Strachan
Thanks for the feedback Raul! More inline... On 21 October 2012 11:58, Raul Kripalani wrote: > Hi James, > > The idea looks nice. I'm just a bit concerned about whether the concept > steps on the toes of the interceptSendToEndpoint DSL to some extent? > > The interceptSTE DSL only triggers at the

[DISCUSS] Message Store

2012-10-23 Thread Christian Ohr
Hi everyone, in the past I came several times across situations that required the one or other kind of Message Store. I noticed that in Camel this doesn't seem to be a "first class citizen" in the sense of a primary architectural concept, which can be applied consistently whereever needed. In sho

Re: [camel-extra] Changed groupId and package name of camel-esper-demo

2012-10-23 Thread Rob Davies
+1 for 2 x e + 1 s On 22 Oct 2012, at 21:05, Henryk Konsek wrote: >> The package name should be >> org.apacheextras (2 'e's, 1 's'). > > Apparently in one of my previous posts I accidentally removed 's' from > the package name. Probably that confused Hadrian. Sorry for that. > > Just to make