Hi All,
I have implemented a camel consumer to take data from my custom application and
send in a camel route.
Now I want my custom application to wait until camel notifies that the message
has been successfully delivered, and sometime wait until the remote component
sends back a response (such
Hi,
If we stick to examples in term of feedback and gateway configuration as an
optional then I understand if ParamUtils.checkDestination(...) returns false
then default values should still be used. Right now
configureApnsCertificate(...) always overrides destinations (with default
values) and tha
On Sat, Sep 8, 2012 at 11:48 AM, gilboy wrote:
> Hi
>
> I am trying to ensure I understand the significance of the ordering of
> routes
>
> Assume I have route #1 which publishes messages on to a SEDA Queue, e.g.
> *from(endpoint).to(sedaQueue)*
>
> and I have route #2 which consumes messages fro
Thanks for your Response Christian
I wonder if there's a nice way to keep all of the functionality of the
current Jdbc aggregator that the sql-component offers, but just change the
way it marshalls the data? Through blueprint property setters
I looked into the source code for this area, and I not
Hi
I am trying to ensure I understand the significance of the ordering of
routes
Assume I have route #1 which publishes messages on to a SEDA Queue, e.g.
*from(endpoint).to(sedaQueue)*
and I have route #2 which consumes messages from the same seda queue, e.g.
*from(sedaQueue).to(endpoint)*.
I
The AggregationRepository do not only store the in message (your xml
payload). It also stores the exchange properties and message headers.
That's the reason why...
If this doesn't fit your needs, you can implement your own
AggregationRepository by implementing
org.apache.camel.spi.AggregationReposi
