Fabric Profile-edit --PID has no effect on the respective container
ashokkumar.tr Apr 29, 2016 4:07 PMI have a Camel context in Blueprint where PID property and default values are defined as follows.
<cm:default-properties>
<cm:property name="brokerURL" value="discovery:(fabric:notifMQGrp)"/>
<cm:property name="topicName" value="TestNotification"/>
</cm:default-properties>
</cm:property-placeholder>
<route id="timerToMQ">
<from uri="timer:foo?period=5000"/>
<log message="Calling direct-vm:producer"/>
<to uri="direct-vm:producer"/>
</route>
<route id="Producer">
<from uri="direct-vm:producer"/>
<setHeader headerName="createdBy">
<constant>ACC</constant>
</setHeader>
<setBody>
<simple>Notification Message from ACC ${date:now:yyyyMMddHHmmssSSS} </simple>
</setBody>
<log message="Calling ActiveMQ ${body}"/>
<to uri="activemq:topic:VirtualTopic.{{topicName}}"/>
<log message="Topic Name is {{topicName}}"/>
</route>
</camelContext>
Camel-context is in a bundle and added in the profile which is assigned to the container. When the container is started, by default the topicName is mapped to TestNotification.
I created a new version of the fabric and edited the profile to set the PID value of topicName as 'NewNotification', and upgrade the container with the new version. But, I don't see the changes are getting applied in the runtime camel-context. I still see the topicName as 'TestNotification' instead of 'NewNotification'.
I do see the changed reflected in the profile.
JBossFuse:admin@ESBRoot> fabric:profile-display test-mq-producer
Version : 1.3
Attributes:
parents: mq-client-notifMQGrp jboss-fuse-full
Containers: managedchild2
Container settings
----------------------------
Repositories :
mvn:test/esb-features/1.0.1/xml/features
Features :
test-mq-producer
Configuration details
----------------------------
PID: test.mq-producer
topicName NewNotification
Other resources
----------------------------
Could you please help to nail down the root cause of the issue?
Thanks,
Ashok