I'd like to move some SEDA endpoint options out of the Camel XML configuration and into a Spring PropertyPlaceholderConfigurer, but I'm struggling a bit.
Here's a snip of the current Camel XML with the URIs I'm trying to configure marked with "-->": <camelContext> <route> <from uri="timer://poller?period=300000" /> <to uri="bean:customerChangeEventService?methodName=getEvents" /> <splitter> <el>${in.body}</el> <idempotentConsumer messageIdRepositoryRef="eventIdRepository"> <el>${in.body.eventId}</el> --> <to uri="seda:customerChangeEvent?size=6000" /> </idempotentConsumer> </splitter> <onException> <exception>java.lang.Throwable</exception> <to uri="seda:eventProcessingErrors"/> </onException> </route> <route> --> <from uri="seda:customerChangeEvent?size=6000" /> ... </route> ... </camelContext> In practice, the configuration may also include the concurrentConsumers option. Optimistically, I configured a PropertyPlaceholderConfigurer and tried changing the URIs to "seda:customerChangeEvent?size=${camel.customer.event.queue.size}", but the property isn't replaced, and camel complains when it tries to convert ${camel.customer.event.queue.size} into an integer. Now I'm struggling trying to configure/instantiate a SedaComponent directly via Spring beans XML. Any pointers to examples? Anyone care to provide a quick example? If it helps, this project is using Camel 1.6.1. TIA, Doug