https in jetty consumer when adding "sslContextParameters" parameters works without specifying a scheme "https"
Hello everyone I don't understand why specifying "https" scheme when https jetty consumer works fine only with "sslContextParameters" parameters. What do I indicate scheme htps or http nothing changes, although the examples indicate what you need https. https://camel.apache.org/components/latest/jetty-component.html [image: image.png] https://camel.apache.org/manual/latest/rest-dsl.html [image: image.png] I use 2.20.2 camel-version This works in simple jetty consumer - -http://0.0.0.0:/http_out?sslContextParameters=#SSLContextParameters";> HTTP - - - - - - And this works in rest dsl to. -http://camel.apache.org/schema/spring"; id="rest"> - - - - - - - -- *With best regards, Mikhail Lukyanov* *Tel: **+7-909-69-71-547*
Salesforce PushTopic subscription replayId not working as expected
Hello, I am attempting to use the camel-salesforce component to subscribe to a Salesforce PushTopic. I am having a couple issues: 1) When I set the replayId = -2 , and when my route starts up there are no existing messages coming in even though there are messages on the PushTopic in the past 24 hrs. I also see this log line: [main] INFO o.a.c.c.s.i.s.SubscriptionHelper - Set Replay extension to replay from `-2` for channel `/topic/AccountUpsert` 2) I update a record in my org to trigger a PushTopic message. My camel route picks up the message. However, I have not been able to access the event object, which includes the replayId of the message. Durable Messaging is an absolute must for our integration, and so we need the replayId. Camel version: 2.22.0 Camel-salesforce version: 2.22.0
Re: configuration of the Pulsar component
thx Andrea,
but if this is the only way to set up a pulsar client via the
camel-pulsar component, it makes
it difficult to use it via the the Spring DSL:
- setting up a client bean doesn't work, because the "factory-method"
can't be directly applied to the client builder call in fluent style
- even if you write some Java code and wrap the call to the builder in a
"getClient" method and use this as "factory-method", you get
a type mismatch, since the "pulsarClient" option is of type
"PulsarClient" (a Java interface), where as the
instantiated bean will an object of the implementing class
==> Is there a way to loosen the type check in Spring to circumvent
this?
Any other ideas how to use camel-pulsar via Spring DSL?
(btw: the "pulsarClient" option is marked as "advanced", it should be
"common", if its the only way to set up a pulsar client)
--Andreas
On 21.01.20 12:46, Andrea Cosentino wrote:
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 giorno mar 21 gen 2020 alle ore 12:37 Andreas Findert <
andreas.find...@web.de> ha scritto:
how to configure the broker URL for the pulsar client instantiated by
the camel-pulsar component?
Re: configuration of the Pulsar component
We have this example based on Spring DSL and Pulsar.
https://github.com/apache/camel/blob/master/examples/camel-example-spring-pulsar/src/main/resources/camel-client.xml
Il giorno gio 23 gen 2020 alle ore 08:32 Andreas Findert <
andreas.find...@web.de> ha scritto:
> thx Andrea,
>
> but if this is the only way to set up a pulsar client via the
> camel-pulsar component, it makes
> it difficult to use it via the the Spring DSL:
>
> - setting up a client bean doesn't work, because the "factory-method"
> can't be directly applied to the client builder call in fluent style
> - even if you write some Java code and wrap the call to the builder in a
> "getClient" method and use this as "factory-method", you get
>a type mismatch, since the "pulsarClient" option is of type
> "PulsarClient" (a Java interface), where as the
>instantiated bean will an object of the implementing class
>==> Is there a way to loosen the type check in Spring to circumvent
> this?
>
> Any other ideas how to use camel-pulsar via Spring DSL?
>
> (btw: the "pulsarClient" option is marked as "advanced", it should be
> "common", if its the only way to set up a pulsar client)
>
> --Andreas
>
> On 21.01.20 12:46, Andrea Cosentino wrote:
> > 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 giorno mar 21 gen 2020 alle ore 12:37 Andreas Findert <
> > andreas.find...@web.de> ha scritto:
> >
> >> how to configure the broker URL for the pulsar client instantiated by
> >> the camel-pulsar component?
> >>
> >>
> >>
>
Re: configuration of the Pulsar component
By the way if you think the documentation should be improved or the
component needs different stuff, open an issue and help by sending a Pull
Request.
Thanks.
Il giorno gio 23 gen 2020 alle ore 08:37 Andrea Cosentino
ha scritto:
> We have this example based on Spring DSL and Pulsar.
>
>
> https://github.com/apache/camel/blob/master/examples/camel-example-spring-pulsar/src/main/resources/camel-client.xml
>
> Il giorno gio 23 gen 2020 alle ore 08:32 Andreas Findert <
> andreas.find...@web.de> ha scritto:
>
>> thx Andrea,
>>
>> but if this is the only way to set up a pulsar client via the
>> camel-pulsar component, it makes
>> it difficult to use it via the the Spring DSL:
>>
>> - setting up a client bean doesn't work, because the "factory-method"
>> can't be directly applied to the client builder call in fluent style
>> - even if you write some Java code and wrap the call to the builder in a
>> "getClient" method and use this as "factory-method", you get
>>a type mismatch, since the "pulsarClient" option is of type
>> "PulsarClient" (a Java interface), where as the
>>instantiated bean will an object of the implementing class
>>==> Is there a way to loosen the type check in Spring to circumvent
>> this?
>>
>> Any other ideas how to use camel-pulsar via Spring DSL?
>>
>> (btw: the "pulsarClient" option is marked as "advanced", it should be
>> "common", if its the only way to set up a pulsar client)
>>
>> --Andreas
>>
>> On 21.01.20 12:46, Andrea Cosentino wrote:
>> > 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 giorno mar 21 gen 2020 alle ore 12:37 Andreas Findert <
>> > andreas.find...@web.de> ha scritto:
>> >
>> >> how to configure the broker URL for the pulsar client instantiated by
>> >> the camel-pulsar component?
>> >>
>> >>
>> >>
>>
>
