I don't think current Camel can do the job 2.
But you can easily write a customer ShutdownStrategy which extends the
default one and configure it into Camel.
On 10/13/10 8:59 PM, ext2 wrote:
Hi:
I have post the question. But it seems I doesn't illustrate the
usage clearly and cause so
There is a sync option which you can use the let the component to be
sync or async.
For the processor, if it does not implement AsyncProcessor interface, it
will be ran synchronously.
You can find more information the component which support the async
option here[1].
[1]http://camel.apache
Hi,
Please see my comments in the mail.
On 10/14/10 1:54 PM, ext2 wrote:
Thanks a lot;
Yes, you are right ;if output is present , it always means result, no matter
what the MEP is;
But this confused my understanding about the exchange pattern;Why we need
the InOnly pattern? Only for performanc
Thanks a lot;
Yes, you are right ;if output is present , it always means result, no matter
what the MEP is;
But this confused my understanding about the exchange pattern;Why we need
the InOnly pattern? Only for performance reason?
If we has no such many patterns, event we didn't define the ME
Then there's something wrong with the aggregator, I'd say.
The result of processing is always: out if present, otherwise in. Makes sense?
I hope this helps,
Hadrian
On Oct 14, 2010, at 12:43 AM, ext2 wrote:
> I still feel it's a bug; let's give a sample as following:
>
>
>
>
>
I still feel it's a bug; let's give a sample as following:
While writing the aggregator, how does I know where the result stored, in or
out message? I can only determine it by exchange pattern;
If the route is using InOnly pattern(which is default), the aggregator w
Does this [1] explain it?
Hadrian
[1] http://camelbot.blogspot.com/2010/10/should-you-getin-or-getout.html
On Oct 13, 2010, at 11:51 PM, ext2 wrote:
> The Transformer Processor always set Out Message as result and doesn't
> care what MEP being;(At least until version camel 2.4.0, it being so,
The Transformer Processor always set Out Message as result and doesn't
care what MEP being;(At least until version camel 2.4.0, it being so, 2.5.0
I haven't checked)
It seems doesn't confirm to the rules of camel's MEP, why?
You most likely need to tell the splitter to use the
UseLatestAggregationStrategy for aggregation if you want it to spit
out the last body,.
On Wed, Oct 13, 2010 at 6:46 PM, ee7arh wrote:
>
> Hello,
>
> This was originally posted in default Camel forum but I guess camel-users is
> best.
>
> Sinc
Hi,
I am in need for a customized Aggregator. Some specific needs are
- one type of (jms) message starts the aggregation
- this message is used to define the logic on what other messages to
correlate. The logic is very dynamic, and might even involve database
lookups
- each aggregation change/even
That's the question. How accommodating should a community be with all the usage
scenarios of its artifacts?
The only solution I see is to engage the smack guys and see what their interest
is, what help they could use and how we could cooperate.
It's apache licensed, so personally I'm willing to h
Hi Traccy,
thanks for the link. The article is quite interesting. In practice we
did not encounter any problems till now but we did not mix several
versions of the same bundle so this could still hit us later.
As far as I understand you should be able to use Aries with camel even
though we us
Would they be the ones to supply osgi-ready bundles? Or could Camel
be bundled with an osgi'd version of the smack jars?
Don
On Wed, Oct 13, 2010 at 1:23 PM, Hadrian Zbarcea wrote:
> You could, but we cannot include it with a dependency on a snapshot.
> I am working on figuring out the best way
Hi all...
If I have a SEDA endpoint set up for not multiple consumers and I use
createConsumer(processor), will that replace the current consumer? Or
simply add a consumer that will never be reached?
Don
Thank you all, I created MessageListenerContainer outside of camel route
which would consume from all external nodes. On message it will create
exchange and post it to camel route using "direct:external".
Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Loadbalancer-fo
There are some caveats when using Spring-DM and OSGI. Guillaume Nodet does a
far better job than I ever could explaining some of the issues in his blog:
http://gnodet.blogspot.com/2010/03/spring-dm-aries-blueprint-and-custom.html
Regards,
Tracy Snell
On Oct 12, 2010, at 3:08 AM, Christian Schne
You could, but we cannot include it with a dependency on a snapshot.
I am working on figuring out the best way to publish 3rd party releases in the
central repo, so that we avoid such issues.
It looks I also need to get in touch with the smack guys and see if they have
any plans for new releases.
I started extending the existing xmpp component to support xmpp pubsub using
a subproject of Smack as supposed by
http://camel.465427.n5.nabble.com/XMPP-pubsub-td3199018.html#a3199018.
The existing Smack trunk includes pubsub support, but it hasn't been
released.
Should I attach a patch ?
Thank
Hello,
This was originally posted in default Camel forum but I guess camel-users is
best.
Since we upgraded to anything from Camel 2.3 onwards, our InOut() routes are
mis-behaving ;)
After some long and painful debugging we realised that the Splitter()
pattern is causing the problem. The proble
Hi:
I have post the question. But it seems I doesn't illustrate the
usage clearly and cause some confuse things. So I re-write the use case,
and repost the subject again. I am regret for it :(.
While the manager decide to stop the applications. They often
encounter such s
Hi:
It seems the camel's graceful shutdownis just like the requirement "robust
stop application": give a waiting time, force stop, and do it's best
ability to avoid lost message;
But the camel cannot support "try to stop" interface; isn't it?
>Hi
>Can you elaborate on the robust shutdown?
>My experience is if you can't do the grace for shutdown with a certain
>time, the on flight exchanges maybe have no other change to be processed.
>Do you mean Camel should store these on flight exchanges into a
>persistence storage, if the wait ti
Hi
Can you elaborate on the robust shutdown?
My experience is if you can't do the grace for shutdown with a certain
time, the on flight exchanges maybe have no other change to be processed.
Do you mean Camel should store these on flight exchanges into a
persistence storage, if the wait time
23 matches
Mail list logo
