What's the effect of having different connectionFactories on JmsComponent, JmsTransactionManager, JmsConfiguration etc
<p>If we have this:</p>

<pre><code>&lt;bean id="txManager" class="org.springframework.jms.connection.JmsTransactionManager"&gt;
    &lt;property name="connectionFactory" ref="pooledConnectionFactory"/&gt;
&lt;/bean&gt;


&lt;bean id="config" class="org.apache.camel.component.jms.JmsConfiguration"&gt;
    &lt;property name="connectionFactory" ref="nonPooledConnectionFactory"/&gt;        
&lt;/bean&gt;

&lt;bean id="myComponent" class="org.apache.camel.component.jms.JmsComponent"&gt;
    &lt;property name="configuration" ref="config"/&gt;       // Which one is used?
    &lt;property name="transactionManager" ref="txManager"/&gt;   // Which one is used?
    &lt;property name="cacheLevelName" value="CACHE_CONSUMER" /&gt;
&lt;/bean&gt;
</code></pre>

<p>Which connectionfactory would be used in a camelroute that uses "myComponent"??
It's transactionmanager references a pooled connnectionfactory, but it's configuration references a non-pooled connectionfactory.</p>

<p>We can set a connectionFactory on so many levels: txManager, JmsComponent, Configuration etc.  Wonder which rule is used for disambiguation if the given one is different?</p>