if you have the bean defined in XML and also the one in Java, then what is
happening is the Java one is "winning" and say is never set.
On Mon, Aug 26, 2019 at 11:24 AM Ron Cecchini
wrote:
> I apologize ahead of time, because I feel like I've taken a few steps
> backward and am now hung up on a
I apologize ahead of time, because I feel like I've taken a few steps backward
and am now hung up on a simple newbie issue regarding application properties
and Spring configuring beans.
Backstory: I've now created about a dozen Camel projects, all reusing the same
basic "architecture" I set up