Re: camel-quartz URL decode

2023-01-12 Thread Claus Ibsen
safe to use URL-encoded parameters > in the same way as, for example, the SFTP component. > It will introduce dependencies to java.net and java.nio: > > import java.net.URLDecoder; > import java.nio.charset.StandardCharsets; > > Peter > > -Ursprungligt meddelande- > Från:

Re: camel-quartz URL decode

2023-01-11 Thread Lindgren Peter
java.net.URLDecoder; import java.nio.charset.StandardCharsets; Peter -Ursprungligt meddelande- Från: Claus Ibsen Skickat: tisdag den 10 januari 2023 20:36 Kopia: dev@camel.apache.org Ämne: [*Newsletter*] Re: camel-quartz URL decode Varning! Externt mail. Klicka inte på länkar eller bifoga

Re: camel-quartz URL decode

2023-01-10 Thread Claus Ibsen
Hi Hmm how are you configuring that quartz endpoint exactly. As it seems you go some custom way with URISupport and encoding and whatnot. You can configure Camel endpoints as basic strings, or use the Endpoint DSL etc. We are not so keen on changing code in endpoint / URI without a compelling

camel-quartz URL decode

2023-01-10 Thread Lindgren Peter
Hello! My first posting on this list, please be gentle  We’ve been using Apache Camel for a short while, and now we have started to use Quartz as the scheduler for SFTP transfers. We have two nodes, and we've decided on the use of Quartz for clustering. To simplify for our developers and