Hi Steve -
I think you’re talking about consuming the property from the Pulsar topic
rather than “within” the Camel route.
If you want the properties to make it into the Pulsar queue, rather than
just in Camel, you’ll need to set PROPERTIES_OUT (add to the key-value
pair) in the header rather
Ah, I just looked at the code, and it doesn't grab any user headers. The
closest thing to user properties or headers that I can find is a field in
the PulsarMessageHeaders class:
@Metadata(label = "producer", description = "The properties of the message
to add.", javaType = "Map")
String
Claus,
I switched to using .withHeader() calls instead of .withProperty(), but I
am still not seeing my headers when I read the message from Pulsar. How
does the Pulsar component attempt to keep track of the headers?
On Fri, Apr 14, 2023 at 10:47 AM Steve973 wrote:
> Claus,
>
> Thanks for
Claus,
Thanks for that. I suppose I was a bit confused about the difference. In
2012, you said (on SO):
> One distinction not mentioned by Ben and Petter is that properties are
> safely stored for the entire duration of the processing of the message in
> Camel. In contrast, headers are part of
Hi
This is expected, exchange properties are local only to the current
Exchange.
If you send data over network protocols like pulsar, kafka, jms then
the payload is only from the message (eg body and headers)
On Thu, Apr 13, 2023 at 11:24 PM Steve973 wrote:
> Hello. I am sending an exchange
Hello. I am sending an exchange with a FluentProducerTemplate to a pulsar
endpoint. When a route reads from that endpoint, the exchange property
that I set is no longer there. This is how I am sending the message:
Exchange exchange = ExchangeBuilder.anExchange(camelContext)
