title: Spring's @Value not working correctly when in CamelConfiguration subclass
body: <p>I noticed a strange behaviour when using <code>@Value</code> with <code>CamelConfiguration</code></p>
  
  <p>Having an example properties file:</p>
  
  <pre><code>test.list=foo,bar,baz
  </code></pre>
  
  <p>and  having a PropertySourcesPlaceholderConfigurer, a ConversionService and when referencing the property in some regular Spring configuration:</p>
  
  <pre><code>@Configuration
  @PropertySource(value = "file:example.properties")
  public class RegularConfig {
  
      @Value("${test.list}")
      List&lt;String&gt; testList;
  
  }
  </code></pre>
  
  <p>Everything works as intended (<code>testList</code> contains three values: <code>foo</code>, <code>bar</code>, and <code>baz</code>), but when the configuration class extends <code>org.apache.camel.spring.javaconfig.CamelConfiguration</code>:</p>
  
  <pre><code>@Configuration
  @PropertySource(value = "file:example.properties")
  public class RegularConfig extends CamelConfiguration {
  
      @Value("${test.list}")
      List&lt;String&gt; testList;
  
  }
  </code></pre>
  
  <p>(see minimal running example for both cases at <a href="https://github.com/michalmela/stackoverflow-questions/tree/master/35719697" rel="nofollow">https://github.com/michalmela/stackoverflow-questions/tree/master/35719697</a>)</p>
  
  <p>the <code>testList</code> contains one, joined value: <code>foo,bar,baz</code>.</p>
  
  <p>Is this a misconfiguration on my side? Or some kind of bug (or feature)?</p>
  
  <p>(I know the obvious workaround is to split the values manually, which is what I already went with, but I'd just like to understand what is going on here)</p>