Re: Passwords in Camel endpoint URIs and limitations of RAW syntax

2020-06-08 Thread Florian Patzl
Hello Vojtech, thanks a lot for your input and updating your solution for 3.x. I chose a slightly different approach by implementing a PropertiesFunction, so that we don't have to place every password in the registry. The PropertiesFunction looks up the password in an pre-existing internal cache

Re: Passwords in Camel endpoint URIs and limitations of RAW syntax

2020-06-04 Thread Florian Patzl
l-example-debezium Regards, Omar On Thu, Jun 4, 2020 at 10:56 AM FabryProg wrote: > Hello Florian, > > Did you try to save the password into a variable / parameter / config file > and lookup it into the URI? > > Kind regards! > > Il giorno gio 4 giu 2020 alle ore 10:50

Re: Passwords in Camel endpoint URIs and limitations of RAW syntax

2020-06-04 Thread Florian Patzl
r detailed problem description. But how is this not solved by URL-Encoding? There was once a bug with URL encodings in Camel. Does this bug still exist? What version of Camel are you using? -Ralf From: Florian Patzl Sent: Wednesday, June 3, 2020 2:49 PM T

Passwords in Camel endpoint URIs and limitations of RAW syntax

2020-06-03 Thread Florian Patzl
Hello, I'm trying to figure out the best way to handle passwords in Camel endpoint URIs in my application. I know the topic has been cause for Stack Overflow posts, JIRA entries and mails but I'm still not sure I've got everything right. Sorry for the big wall of text, but I think I should explai

Messages with byte[] bodies are sent as "large messages" to Artemis via camel-jms and cause ConsumerTemplate exception

2020-01-13 Thread Florian Patzl
Hello, I've stumbled upon behavior in Camel + Artemis JMS that I do not understand. Camel messages with bodies of type byte[] are treated as "large messages" in Artemis - even small messages with only three bytes. In combination with "manually" polling the messages from JMS using a Camel Consumer