Just to close the loop, here is what I did:
<bean
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"><!--
<property name="order" value="0"/>
--><property name="location"
value="classpath:acquirer-config.properties"/>
</bean>
<bean id="camel" class="org.apache.camel.spring.CamelContextFactoryBean"
depends-on="my_other_bean">
<property name="trace" value="false"/>
<property name="packageScan">
<bean class="com.mypackage.CamelPackageScanDefinition">
<property
name="packageList"><value>${route.packageScan}</value></property>
</bean>
</property>
</bean>
<bean id="template"
class="org.apache.camel.spring.CamelProducerTemplateFactoryBean">
<property name="camelContext" ref="camel"/>
</bean>
where the CamelPackageScanDefinition is a subclass of the
org.apache.camel.model.PackageScanDefinition class, which adds the necessary
setter methods, as well as additional property to allow me to set multiple
packages using a space separated string.
I've created a new ticket for tracking this:
https://issues.apache.org/activemq/browse/CAMEL-1997
https://issues.apache.org/activemq/browse/CAMEL-1997
--
View this message in context:
http://www.nabble.com/Use-regular-spring-bean-definition-style-rather-than-xbean-camelContext-style-tp25305561p25355599.html
Sent from the Camel - Users mailing list archive at Nabble.com.
