Check out http://camel.apache.org/splitter.html and look for the paragraph
Split aggregate request/reply sample
Here you have an example of a splitter using a custom aggregation strategy.
In your aggregation strategy, you have to make sure the CamelSplitSize
property is set on the exchange you
properties are getting not reloaded in case of spring dm.it works fine in
case of blue print xml and properties are reloaded when changes happen and
deploy the profile in jboss fuse.
in blueprint cm:property-placeholder is having update-strategy attribute
which does the properties reloaded where
Have a look at [1], section 9.1.2.1.
[1]
http://docs.spring.io/spring-osgi/docs/1.2.0-m2/reference/html/compendium.html
Raúl.
On 15 Aug 2015 09:29, chaituu yarlagadd...@gmail.com wrote:
properties are getting not reloaded in case of spring dm.it works fine in
case of blue print xml and
Thanks for the reply.actually i saw this page but quite didn't understood
it.Do i need to create ContainerManagedBean class to make use of properties
getting reloaded.but in case of blueprint we have not created any sort of
this class right.
bean id=containerManaged class=ContainerManagedBean
