Hi,
You are welcome to do so. Please raise a JIRA ticket and then send your PR.
Regards,
Omar
On Mon, Jan 20, 2020 at 4:15 PM Jonathan Schoreels <
jonathan.schore...@gmail.com> wrote:
> Hi,
>
> Currently, the camel-rabbitmq endpoints, if set as "bridgeEndpoint",
> ignores the following exchange
how to configure the broker URL for the pulsar client instantiated by
the camel-pulsar component?
You need to create your own pulsarClient component option and set it on
your component
PulsarClient client = PulsarClient.builder()
.serviceUrl("pulsar://localhost:6650,localhost:6651,localhost:6652")
.build();
Then you can add this to your component configuration.
Il gi
Hi,
I moved from 2.x to 3.x and see getOut() on exchange is now depreciated.
But the intention to replace it with getMessage is not inline with the
behaviour of getOut().
https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_getout_on_message
As stated in above link the getMessage
Dear Apache enthusiast,
(You’re receiving this message because you are subscribed to one or more
project mailing lists at the Apache Software Foundation.)
The call for presentations for ApacheCon North America 2020 is now open
at https://apachecon.com/acna2020/cfp
ApacheCon will be held at
Hi,
Any help on this?
On Tue, Jan 21, 2020 at 5:56 PM Narsi Reddy Nallamilli <
narsi.nallami...@gmail.com> wrote:
> Hi,
>
> I moved from 2.x to 3.x and see getOut() on exchange is now depreciated.
> But the intention to replace it with getMessage is not inline with the
> behaviour of getOut().
>
