Thanks you Claus and Zoran,
You are correct and in the end it does appear it was a problem in my
properties file.
I actually implemented a bridging property resolver but it just conflicted
with the one created by spring boot.
Thanks again,
Jared
On Fri., Dec. 11, 2020, 02:46 Zoran Regvart, wr
Hi Jared
On Thu, Dec 10, 2020 at 7:49 PM Jared Whiklo wrote:
> Well played Zoran, well played.
Thanks :) We aim to please :)
> Ok as I wait for IntelliJ to finish digesting Camel I have two follow-up
> questions
Oh, I hope you didn't try to import the whole project, I usually just
open the mod
Hi
In spring boot then properties works just like regular spring
properties. You can put them in application.properties and use them in
your Camel routes via {{keyName}}.
There is no need to do any special setup.
That link your point to about bridging that was the old days with
spring XML (not sp
Well played Zoran, well played.
Ok as I wait for IntelliJ to finish digesting Camel I have two follow-up
questions
1. Digging in some more, perhaps this is more my expectations.
I am using a @Configuration class with @PropertySources.
In my RouteBuilder I have some existing @PropertyInject v
Hi Jared,
thanks for bringing this to our attention, I'm sure that we have more
of these issues throughout the documentation.
I'm looking at the old source[1] of documentation and for whatever
reason the formatting is broken there, so that could be the reason why
when we migrated the page over to
