Sunil - I asked about the property placeholders because there were a lot of issues with CamelBlueprintTestSupport, property placeholders and synchronization. I think these issues have been resolved in the later versions of Camel.
Is it possible to test the route using Camel 2.16.1 to see if you’re hitting one of the issues that has been corrected? Also - earlier in the thread you mentioned something about using context.addComponent to register the “ibmmq” component. I think you could provide that component by overriding the addServicesOnStartup method of CamelBlueprintTestSupport. - Quinn > On Jan 26, 2016, at 6:17 PM, web_nab...@sunilsamuel.com wrote: > > Hi Quinn, > > Sorry I did not see this comment. I configure the /etc folder within JBoss > Fuse to provide this information. That part is working fine though. > > Thanks, > Sunil. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/WMQ-CamelBlueprintTestSupport-tp5774845p5776758.html > Sent from the Camel Development mailing list archive at Nabble.com.
