The claim check pattern is a bit more complex that. I will be touching
on it in my presentation at ApacheCon next week.
Cheers,
Hadrian
On 02/21/2013 06:26 PM, Christian Ohr wrote:
HI Henryk,
A claim check EIP is definitely an excellent use case for a message store.
Regarding your example -
I'll update the wiki.
Christian
Am 22.02.2013 16:32 schrieb "Henryk Konsek" :
> If nobody objects with our latest ideas, it will be good to push them
> to the wiki page. Christian, would you handle this or should I do it
> on your behalf?
>
> Have a nice weekend :) .
>
> --
> Henryk Konsek
> http
If nobody objects with our latest ideas, it will be good to push them
to the wiki page. Christian, would you handle this or should I do it
on your behalf?
Have a nice weekend :) .
--
Henryk Konsek
http://henryk-konsek.blogspot.com
> Christian M.:
> Shouldn't it be possible to configure the store?
Yes, it definitely should be. My examples do not aspire to be complete
:) . However we should also provide a way to configure the default
store on both Context and Route level.
> Christian M.:
> By default (if no message store ins
HI Henryk,
A claim check EIP is definitely an excellent use case for a message store.
Regarding your example - it is probably a matter of taste, but I would rather
* register a (global) default message store with the CamelContext
rather than in the route
* allow all applicable EIPs to override th
How about making the Claim Check EIP Expression-Aware?
Then one could do something like, which is more versatile and higher-level:
from("...")
.claimCheck(myMessageStoreInstance,
xpath("/MyCoolElement/@superCoolAttribute"))
.to("");
and
from("...")
.claim(myMessageStoreInstance, ognl("
Yes, this should always be possible. But registering a (default) store
in the Camel Context might be an alternative, e.g. like it is done
with a ThreadPoolFactory. If you don't explicitly provide one, the
default one is taken.
(the other) Christian
2013/2/21 Christian Müller :
> Shouldn't it be p
Shouldn't it be possible to configure the store?
Something like:
from("...")
.claimCheck(myMessageStoreInstance)
.to("");
and
from("...")
.setHeader(Exchange.CLAIM_CHECK, constant("my claim check id"))
.claim(myMessageStoreInstance)
.to("");
By default (if no message store ins
> You are invited add, comment, criticize etc.
Hi Christian,
Looks good :) .
I've added some examples to Wiki demonstrating my vision of the usage
of Claim Check EIP.
// Setting default message store for route:
defaultMessageStore(myStore);
// Claim Check EIP store:
// 1) Store body.
// 2) Set
Hi folks,
at last I managed to set up a Wiki page for discussing Camel 3 Message
Store. Here is is:
https://cwiki.apache.org/confluence/display/CAMEL/Camel+3.0+-+Message+Store
You are invited add, comment, criticize etc. The more thoughts and
ideas we get, the more likely it is to cover the user
> Christian:
> I'll post here again when I'm done.
Great, I'm looking forward to receive your message then :) .
> Willem:
> +1 to start the idea in wiki.
Actually it will be nice if all "ideas" champions could create such
aggregation wiki pages for their topics (and link them from the "Camel
3.0
3
> An: dev@camel.apache.org (mailto:dev@camel.apache.org)
> Betreff: Re: Message History EIP/Message Store status
>
> Hi,
>
> I will add a Wiki page regarding this topic within the next days and
> aggegate all current thoughts and ideas. Everyone is invited to contribute,
> of course
33
An: dev@camel.apache.org
Betreff: Re: Message History EIP/Message Store status
Hi,
I will add a Wiki page regarding this topic within the next days and
aggegate all current thoughts and ideas. Everyone is invited to contribute,
of course!
I'll post here again when I'm done.
cheers
Christian
201
Hi,
I will add a Wiki page regarding this topic within the next days and
aggegate all current thoughts and ideas. Everyone is invited to
contribute, of course!
I'll post here again when I'm done.
cheers
Christian
2013/2/17 Henryk Konsek :
> Hi,
>
> Is there a single place (wiki page for example)
14 matches
Mail list logo
