> -----Original Message----- > From: Claus Ibsen [mailto:[email protected]] > Sent: Tuesday, October 18, 2016 1:52 PM > To: [email protected] > Subject: Re: Clarify why lazy-loaded component mapping files are > properties files that aren't labeled as such > > Hi > > Welcome to the Camel community. > > Those files are for Camel component developers. The file is used for > component discovery so Camel can automatic find components from the > classpath. > > As a Camel *end user* you should not use those files. Instead if you > want to configure Camel components / routes / endpoints etc you can do > that in many ways. For example using property placeholders which you can > read about here: > http://camel.apache.org/using-propertyplaceholder.html
Uh, ok. None of that has anything to do with my question. > On Mon, Oct 17, 2016 at 6:30 PM, KARR, DAVID <[email protected]> wrote: > > I haven't really used Camel yet, I'm just reading the manual to > familiarize myself with it, as some projects I'll be working with use > it. > > > > I noticed that the way you define the lazy-loaded mappings for > components uses properties files that aren't labeled as properties > files. For instance, to define the mapping for a component named "foo", > you place a file named just "foo" in "META- > INF/services/org/apache/camel/component", instead of "foo.properties". > > > > I can deal with this, but it just seems odd. Is there any background > on why it was done this way? > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
