You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Gert Vanthienen <ge...@gmail.com> on 2013/07/19 12:20:43 UTC
[PROPOSAL] Camel Container SPI in ServiceMix 5
L.S.,
A few weeks ago, Claus mentioned that Guillaume's changes for the
original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
cfr. https://issues.apache.org/jira/browse/CAMEL-6115
Last week (when I was on vacation) and this week, I had some time
available to play with this a bit and ended up with
https://github.com/gertv/servicemix5/tree/container-spi - this
includes some of the original ServiceMix 5 codebase as well as some
other bits to make this global interceptor mechanism an out-of-box
feature of ServiceMix
With this code in place, the Container SPI is implemented by
ServiceMix and started as soon as possible during container start-up.
This way, users can register Camel Processor instances to be used as
global interceptors. There also is a similar mechanism to contribute
custom InterceptorStrategy implementations and interact with the
ProcessorFactory mechanism.
As a proof-of-concept, I also added a MongoDB auditor that stores all
processed exchanges in MongoDB, grouped by breadcrumb id, so people
have the entire exchange flow audited nicely together. This seems to
work very nicely and you can enable/disable the mechanism at runtime.
There's obviously quite a bit of work to be done before we can
actually release this (some extra features like camelcontext filtering
on the interceptor would be nice and especially docs are missing), but
I think it would make a really nice addition to ServiceMix 5. It
would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
whenever that becomes available, but in my mind, that slight delay
should be well worth it.
Wdyt?
Gert Vanthienen
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Claus Ibsen <cl...@gmail.com>.
+1
On Fri, Jul 19, 2013 at 12:20 PM, Gert Vanthienen
<ge...@gmail.com> wrote:
> L.S.,
>
>
> A few weeks ago, Claus mentioned that Guillaume's changes for the
> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>
> Last week (when I was on vacation) and this week, I had some time
> available to play with this a bit and ended up with
> https://github.com/gertv/servicemix5/tree/container-spi - this
> includes some of the original ServiceMix 5 codebase as well as some
> other bits to make this global interceptor mechanism an out-of-box
> feature of ServiceMix
>
> With this code in place, the Container SPI is implemented by
> ServiceMix and started as soon as possible during container start-up.
> This way, users can register Camel Processor instances to be used as
> global interceptors. There also is a similar mechanism to contribute
> custom InterceptorStrategy implementations and interact with the
> ProcessorFactory mechanism.
>
> As a proof-of-concept, I also added a MongoDB auditor that stores all
> processed exchanges in MongoDB, grouped by breadcrumb id, so people
> have the entire exchange flow audited nicely together. This seems to
> work very nicely and you can enable/disable the mechanism at runtime.
>
> There's obviously quite a bit of work to be done before we can
> actually release this (some extra features like camelcontext filtering
> on the interceptor would be nice and especially docs are missing), but
> I think it would make a really nice addition to ServiceMix 5. It
> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
> whenever that becomes available, but in my mind, that slight delay
> should be well worth it.
>
>
> Wdyt?
>
> Gert Vanthienen
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
Regards
JB
On 07/19/2013 12:20 PM, Gert Vanthienen wrote:
> L.S.,
>
>
> A few weeks ago, Claus mentioned that Guillaume's changes for the
> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>
> Last week (when I was on vacation) and this week, I had some time
> available to play with this a bit and ended up with
> https://github.com/gertv/servicemix5/tree/container-spi - this
> includes some of the original ServiceMix 5 codebase as well as some
> other bits to make this global interceptor mechanism an out-of-box
> feature of ServiceMix
>
> With this code in place, the Container SPI is implemented by
> ServiceMix and started as soon as possible during container start-up.
> This way, users can register Camel Processor instances to be used as
> global interceptors. There also is a similar mechanism to contribute
> custom InterceptorStrategy implementations and interact with the
> ProcessorFactory mechanism.
>
> As a proof-of-concept, I also added a MongoDB auditor that stores all
> processed exchanges in MongoDB, grouped by breadcrumb id, so people
> have the entire exchange flow audited nicely together. This seems to
> work very nicely and you can enable/disable the mechanism at runtime.
>
> There's obviously quite a bit of work to be done before we can
> actually release this (some extra features like camelcontext filtering
> on the interceptor would be nice and especially docs are missing), but
> I think it would make a really nice addition to ServiceMix 5. It
> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
> whenever that becomes available, but in my mind, that slight delay
> should be well worth it.
>
>
> Wdyt?
>
> Gert Vanthienen
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Freeman Fang <fr...@gmail.com>.
+1
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋
On 2013-7-19, at 下午6:20, Gert Vanthienen wrote:
> L.S.,
>
>
> A few weeks ago, Claus mentioned that Guillaume's changes for the
> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>
> Last week (when I was on vacation) and this week, I had some time
> available to play with this a bit and ended up with
> https://github.com/gertv/servicemix5/tree/container-spi - this
> includes some of the original ServiceMix 5 codebase as well as some
> other bits to make this global interceptor mechanism an out-of-box
> feature of ServiceMix
>
> With this code in place, the Container SPI is implemented by
> ServiceMix and started as soon as possible during container start-up.
> This way, users can register Camel Processor instances to be used as
> global interceptors. There also is a similar mechanism to contribute
> custom InterceptorStrategy implementations and interact with the
> ProcessorFactory mechanism.
>
> As a proof-of-concept, I also added a MongoDB auditor that stores all
> processed exchanges in MongoDB, grouped by breadcrumb id, so people
> have the entire exchange flow audited nicely together. This seems to
> work very nicely and you can enable/disable the mechanism at runtime.
>
> There's obviously quite a bit of work to be done before we can
> actually release this (some extra features like camelcontext filtering
> on the interceptor would be nice and especially docs are missing), but
> I think it would make a really nice addition to ServiceMix 5. It
> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
> whenever that becomes available, but in my mind, that slight delay
> should be well worth it.
>
>
> Wdyt?
>
> Gert Vanthienen
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Freeman Fang <fr...@gmail.com>.
+1
Thanks
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋
On 2013-7-26, at 下午11:38, Wim Verreydt wrote:
>
> Sounds like a great feature!
>
> Anyone any objection if I try to implement a EHCache version of the inceptor?
> I made a jira issue for it: https://issues.apache.org/jira/browse/SM-2208
>
> Wim
>
>
> On 19 Jul 2013, at 13:55, Gert Vanthienen <ge...@gmail.com> wrote:
>
>> Hey Rob,
>>
>> The current MongoDB auditor is an optional feature, so it's only
>> enabled if people install and configure it, but you're right: having a
>> second, cache-based auditor around for testing/development purposes
>> would definitely be a good idea.
>>
>> Thanks,
>>
>> Gert
>>
>>
>> On Fri, Jul 19, 2013 at 12:39 PM, Robert Davies <ra...@gmail.com> wrote:
>>> this looks really good - maybe we could use a cache instead (like EHCache) - for testing/default ? - but I'm for skipping Camel 2.11 and going to 2.12
>>>
>>> On 19 Jul 2013, at 11:20, Gert Vanthienen <ge...@gmail.com> wrote:
>>>
>>>> L.S.,
>>>>
>>>>
>>>> A few weeks ago, Claus mentioned that Guillaume's changes for the
>>>> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
>>>> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>>>>
>>>> Last week (when I was on vacation) and this week, I had some time
>>>> available to play with this a bit and ended up with
>>>> https://github.com/gertv/servicemix5/tree/container-spi - this
>>>> includes some of the original ServiceMix 5 codebase as well as some
>>>> other bits to make this global interceptor mechanism an out-of-box
>>>> feature of ServiceMix
>>>>
>>>> With this code in place, the Container SPI is implemented by
>>>> ServiceMix and started as soon as possible during container start-up.
>>>> This way, users can register Camel Processor instances to be used as
>>>> global interceptors. There also is a similar mechanism to contribute
>>>> custom InterceptorStrategy implementations and interact with the
>>>> ProcessorFactory mechanism.
>>>>
>>>> As a proof-of-concept, I also added a MongoDB auditor that stores all
>>>> processed exchanges in MongoDB, grouped by breadcrumb id, so people
>>>> have the entire exchange flow audited nicely together. This seems to
>>>> work very nicely and you can enable/disable the mechanism at runtime.
>>>>
>>>> There's obviously quite a bit of work to be done before we can
>>>> actually release this (some extra features like camelcontext filtering
>>>> on the interceptor would be nice and especially docs are missing), but
>>>> I think it would make a really nice addition to ServiceMix 5. It
>>>> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
>>>> whenever that becomes available, but in my mind, that slight delay
>>>> should be well worth it.
>>>>
>>>>
>>>> Wdyt?
>>>>
>>>> Gert Vanthienen
>>>
>
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Wim Verreydt <wi...@studentenleuven.be>.
Sounds like a great feature!
Anyone any objection if I try to implement a EHCache version of the inceptor?
I made a jira issue for it: https://issues.apache.org/jira/browse/SM-2208
Wim
On 19 Jul 2013, at 13:55, Gert Vanthienen <ge...@gmail.com> wrote:
> Hey Rob,
>
> The current MongoDB auditor is an optional feature, so it's only
> enabled if people install and configure it, but you're right: having a
> second, cache-based auditor around for testing/development purposes
> would definitely be a good idea.
>
> Thanks,
>
> Gert
>
>
> On Fri, Jul 19, 2013 at 12:39 PM, Robert Davies <ra...@gmail.com> wrote:
>> this looks really good - maybe we could use a cache instead (like EHCache) - for testing/default ? - but I'm for skipping Camel 2.11 and going to 2.12
>>
>> On 19 Jul 2013, at 11:20, Gert Vanthienen <ge...@gmail.com> wrote:
>>
>>> L.S.,
>>>
>>>
>>> A few weeks ago, Claus mentioned that Guillaume's changes for the
>>> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
>>> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>>>
>>> Last week (when I was on vacation) and this week, I had some time
>>> available to play with this a bit and ended up with
>>> https://github.com/gertv/servicemix5/tree/container-spi - this
>>> includes some of the original ServiceMix 5 codebase as well as some
>>> other bits to make this global interceptor mechanism an out-of-box
>>> feature of ServiceMix
>>>
>>> With this code in place, the Container SPI is implemented by
>>> ServiceMix and started as soon as possible during container start-up.
>>> This way, users can register Camel Processor instances to be used as
>>> global interceptors. There also is a similar mechanism to contribute
>>> custom InterceptorStrategy implementations and interact with the
>>> ProcessorFactory mechanism.
>>>
>>> As a proof-of-concept, I also added a MongoDB auditor that stores all
>>> processed exchanges in MongoDB, grouped by breadcrumb id, so people
>>> have the entire exchange flow audited nicely together. This seems to
>>> work very nicely and you can enable/disable the mechanism at runtime.
>>>
>>> There's obviously quite a bit of work to be done before we can
>>> actually release this (some extra features like camelcontext filtering
>>> on the interceptor would be nice and especially docs are missing), but
>>> I think it would make a really nice addition to ServiceMix 5. It
>>> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
>>> whenever that becomes available, but in my mind, that slight delay
>>> should be well worth it.
>>>
>>>
>>> Wdyt?
>>>
>>> Gert Vanthienen
>>
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Gert Vanthienen <ge...@gmail.com>.
Hey Rob,
The current MongoDB auditor is an optional feature, so it's only
enabled if people install and configure it, but you're right: having a
second, cache-based auditor around for testing/development purposes
would definitely be a good idea.
Thanks,
Gert
On Fri, Jul 19, 2013 at 12:39 PM, Robert Davies <ra...@gmail.com> wrote:
> this looks really good - maybe we could use a cache instead (like EHCache) - for testing/default ? - but I'm for skipping Camel 2.11 and going to 2.12
>
> On 19 Jul 2013, at 11:20, Gert Vanthienen <ge...@gmail.com> wrote:
>
>> L.S.,
>>
>>
>> A few weeks ago, Claus mentioned that Guillaume's changes for the
>> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
>> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>>
>> Last week (when I was on vacation) and this week, I had some time
>> available to play with this a bit and ended up with
>> https://github.com/gertv/servicemix5/tree/container-spi - this
>> includes some of the original ServiceMix 5 codebase as well as some
>> other bits to make this global interceptor mechanism an out-of-box
>> feature of ServiceMix
>>
>> With this code in place, the Container SPI is implemented by
>> ServiceMix and started as soon as possible during container start-up.
>> This way, users can register Camel Processor instances to be used as
>> global interceptors. There also is a similar mechanism to contribute
>> custom InterceptorStrategy implementations and interact with the
>> ProcessorFactory mechanism.
>>
>> As a proof-of-concept, I also added a MongoDB auditor that stores all
>> processed exchanges in MongoDB, grouped by breadcrumb id, so people
>> have the entire exchange flow audited nicely together. This seems to
>> work very nicely and you can enable/disable the mechanism at runtime.
>>
>> There's obviously quite a bit of work to be done before we can
>> actually release this (some extra features like camelcontext filtering
>> on the interceptor would be nice and especially docs are missing), but
>> I think it would make a really nice addition to ServiceMix 5. It
>> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
>> whenever that becomes available, but in my mind, that slight delay
>> should be well worth it.
>>
>>
>> Wdyt?
>>
>> Gert Vanthienen
>
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Robert Davies <ra...@gmail.com>.
this looks really good - maybe we could use a cache instead (like EHCache) - for testing/default ? - but I'm for skipping Camel 2.11 and going to 2.12
On 19 Jul 2013, at 11:20, Gert Vanthienen <ge...@gmail.com> wrote:
> L.S.,
>
>
> A few weeks ago, Claus mentioned that Guillaume's changes for the
> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>
> Last week (when I was on vacation) and this week, I had some time
> available to play with this a bit and ended up with
> https://github.com/gertv/servicemix5/tree/container-spi - this
> includes some of the original ServiceMix 5 codebase as well as some
> other bits to make this global interceptor mechanism an out-of-box
> feature of ServiceMix
>
> With this code in place, the Container SPI is implemented by
> ServiceMix and started as soon as possible during container start-up.
> This way, users can register Camel Processor instances to be used as
> global interceptors. There also is a similar mechanism to contribute
> custom InterceptorStrategy implementations and interact with the
> ProcessorFactory mechanism.
>
> As a proof-of-concept, I also added a MongoDB auditor that stores all
> processed exchanges in MongoDB, grouped by breadcrumb id, so people
> have the entire exchange flow audited nicely together. This seems to
> work very nicely and you can enable/disable the mechanism at runtime.
>
> There's obviously quite a bit of work to be done before we can
> actually release this (some extra features like camelcontext filtering
> on the interceptor would be nice and especially docs are missing), but
> I think it would make a really nice addition to ServiceMix 5. It
> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
> whenever that becomes available, but in my mind, that slight delay
> should be well worth it.
>
>
> Wdyt?
>
> Gert Vanthienen
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Willem jiang <wi...@gmail.com>.
+1 to use the Camel 2.12.x.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Friday, July 19, 2013 at 6:20 PM, Gert Vanthienen wrote:
> L.S.,
>
>
> A few weeks ago, Claus mentioned that Guillaume's changes for the
> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>
> Last week (when I was on vacation) and this week, I had some time
> available to play with this a bit and ended up with
> https://github.com/gertv/servicemix5/tree/container-spi - this
> includes some of the original ServiceMix 5 codebase as well as some
> other bits to make this global interceptor mechanism an out-of-box
> feature of ServiceMix
>
> With this code in place, the Container SPI is implemented by
> ServiceMix and started as soon as possible during container start-up.
> This way, users can register Camel Processor instances to be used as
> global interceptors. There also is a similar mechanism to contribute
> custom InterceptorStrategy implementations and interact with the
> ProcessorFactory mechanism.
>
> As a proof-of-concept, I also added a MongoDB auditor that stores all
> processed exchanges in MongoDB, grouped by breadcrumb id, so people
> have the entire exchange flow audited nicely together. This seems to
> work very nicely and you can enable/disable the mechanism at runtime.
>
> There's obviously quite a bit of work to be done before we can
> actually release this (some extra features like camelcontext filtering
> on the interceptor would be nice and especially docs are missing), but
> I think it would make a really nice addition to ServiceMix 5. It
> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
> whenever that becomes available, but in my mind, that slight delay
> should be well worth it.
>
>
> Wdyt?
>
> Gert Vanthienen
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Christian Müller <ch...@gmail.com>.
+1
Best,
Christian
Am 19.07.2013 12:21 schrieb "Gert Vanthienen" <ge...@gmail.com>:
> L.S.,
>
>
> A few weeks ago, Claus mentioned that Guillaume's changes for the
> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>
> Last week (when I was on vacation) and this week, I had some time
> available to play with this a bit and ended up with
> https://github.com/gertv/servicemix5/tree/container-spi - this
> includes some of the original ServiceMix 5 codebase as well as some
> other bits to make this global interceptor mechanism an out-of-box
> feature of ServiceMix
>
> With this code in place, the Container SPI is implemented by
> ServiceMix and started as soon as possible during container start-up.
> This way, users can register Camel Processor instances to be used as
> global interceptors. There also is a similar mechanism to contribute
> custom InterceptorStrategy implementations and interact with the
> ProcessorFactory mechanism.
>
> As a proof-of-concept, I also added a MongoDB auditor that stores all
> processed exchanges in MongoDB, grouped by breadcrumb id, so people
> have the entire exchange flow audited nicely together. This seems to
> work very nicely and you can enable/disable the mechanism at runtime.
>
> There's obviously quite a bit of work to be done before we can
> actually release this (some extra features like camelcontext filtering
> on the interceptor would be nice and especially docs are missing), but
> I think it would make a really nice addition to ServiceMix 5. It
> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
> whenever that becomes available, but in my mind, that slight delay
> should be well worth it.
>
>
> Wdyt?
>
> Gert Vanthienen
>
Re: [PROPOSAL] Camel Container SPI in ServiceMix 5
Posted by Jon Anstey <ja...@gmail.com>.
+1 Looks cool!
On Fri, Jul 19, 2013 at 7:50 AM, Gert Vanthienen
<ge...@gmail.com>wrote:
> L.S.,
>
>
> A few weeks ago, Claus mentioned that Guillaume's changes for the
> original ServiceMix 5 build were now available in Camel 2.12-SNAPSHOT,
> cfr. https://issues.apache.org/jira/browse/CAMEL-6115
>
> Last week (when I was on vacation) and this week, I had some time
> available to play with this a bit and ended up with
> https://github.com/gertv/servicemix5/tree/container-spi - this
> includes some of the original ServiceMix 5 codebase as well as some
> other bits to make this global interceptor mechanism an out-of-box
> feature of ServiceMix
>
> With this code in place, the Container SPI is implemented by
> ServiceMix and started as soon as possible during container start-up.
> This way, users can register Camel Processor instances to be used as
> global interceptors. There also is a similar mechanism to contribute
> custom InterceptorStrategy implementations and interact with the
> ProcessorFactory mechanism.
>
> As a proof-of-concept, I also added a MongoDB auditor that stores all
> processed exchanges in MongoDB, grouped by breadcrumb id, so people
> have the entire exchange flow audited nicely together. This seems to
> work very nicely and you can enable/disable the mechanism at runtime.
>
> There's obviously quite a bit of work to be done before we can
> actually release this (some extra features like camelcontext filtering
> on the interceptor would be nice and especially docs are missing), but
> I think it would make a really nice addition to ServiceMix 5. It
> would require us to skip Camel 2.11.x and go straight for Camel 2.12.x
> whenever that becomes available, but in my mind, that slight delay
> should be well worth it.
>
>
> Wdyt?
>
> Gert Vanthienen
>
--
Cheers,
Jon
---------------
Red Hat, Inc.
Email: janstey@redhat.com
Web: http://redhat.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen