Thanks. Works perfectly. ________________________________ From: Claus Ibsen <claus.ib...@gmail.com> Sent: Sunday, June 7, 2020 10:01 To: users@camel.apache.org <users@camel.apache.org> Subject: [EXTERNAL] - Re: hash (pound sign) notation in Camel 3.x
Hi You should use #bean:xxx to refer to a bean in the registry by its id. https://urldefense.com/v3/__https://github.com/apache/camel/commit/763bfeb999f1fa7a3a3f1ef96c7a7eefa2032734__;!!Obbck6kTJA!P57o44tdLPjkMBevUjgX2hR98fYAijroozT90KDqfGVRXVzdFKKgDHAxegBR-O_0$ On Fri, Jun 5, 2020 at 1:56 PM Vojtech Fried <vfr...@opentext.com.invalid> wrote: > > Hi, > > in Camel 2.x I used a #<name> notation in URIs for endpoints. I used the > #<name> for example for passwords, because passwords can contain any > characters and I don't want any Camel processing on it. I used SimpleRegistry > to add objects and somehow plugged it into Camel context and then looked > those object by name with #<name>. It does not seem to work in 3.x. The > replacement for this seems to be ${ref:<name>} notation. But it works > differently, at least for my "toD" URIs. If I put a String into the registry > and reference it with "ref:", it is somehow processed by Camel when it > normalizes URIs, I think properties are looked up if the string contains > something like {{name}}. > > Is there any documentation on "#" or "ref"? Was "#" replaced with "ref" in > 3.x or is it some problem in my environment? I haven't found it in migration > to 3 docs. > > /Vojtech -- Claus Ibsen ----------------- https://urldefense.com/v3/__http://davsclaus.com__;!!Obbck6kTJA!P57o44tdLPjkMBevUjgX2hR98fYAijroozT90KDqfGVRXVzdFKKgDHAxevVC1KEJ$ @davsclaus Camel in Action 2: https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!Obbck6kTJA!P57o44tdLPjkMBevUjgX2hR98fYAijroozT90KDqfGVRXVzdFKKgDHAxejVYAWjR$
