I'll have a look at that Christian. As I'm using spring config I assumed I
could change properties by using getBean as that's how spring config works
normally. Camel seems to use a different set of bean instances even though it
seems to load them via spring.
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 5 Jul 2011, at 22:43, Christian Müller wrote:
> Why not using the PropertyPlaceholder mechanism and providing a config file
> for test? That's the way we handle properties which changes from one
> environment to another.
> Am 04.07.2011 15:56 schrieb "Alistair Young" <alistair.yo...@uhi.ac.uk>:
>> Camel seems to load its own instances of beans in camel-config.xml
>>
>> testProcessor = (TestProcessor)ctx.getBean("testProcessor");
>> testProcessor.setPath("/home/test");
>>
>> but when i do this:
>>
>> sendBody("activemq:topic:edirectoryprocessed", testuserCreatePayload);
>>
>> testProcessor has its old path. i.e. testProcessor.setPath("/home/test")
> has no effect in camel
>>
>> is there a way to load bean definition that camel will use during the
> test?
>>
>> thanks,
>>
>> Alistair
>>
>>
>> --
>> mov eax,1
>> mov ebx,0
>> int 80h
>>
>>
>>
>>
