Apologize for the double post. I believe I am posting in the right place now.
I am experiencing the same issues referred to in Jira ticket KARAF-1190 in Cellar version 2.2.5. When I create the configuration from the managed factory service, the original output looks like this: PID = My_Config_20.41122af6-f28c-48cc-bba9-2262fbdd033f Factory PID = My_Config_20 BundleLocation = mvn:my.program.soap/program-soap-endpoint20events/1.2.2-SNAPSHOT deliveryMethodUrl = http://192.168.1.113:8080/mockprogramEventConsumerBinding?WSDL filterXml = blah service.factoryPid = My_Config_20 service.pid = My_Config_20.41122af6-f28c-48cc-bba9-2262fbdd033f ConfigId = my.contextual.id ConfigUuid = my.contextual.id|http://192.168.1.113:8080/mockprogram?WSDL When Cellar replicates the configuration to another server I get the following: PID = My_Config_20.41122af6-f28c-48cc-bba9-2262fbdd033f BundleLocation = Unbound deliveryMethodUrl = http://192.168.1.113:8080/mockprogramEventConsumerBinding?WSDL filterXml = blah service.pid = My_Config_20.41122af6-f28c-48cc-bba9-2262fbdd033f ConfigId = my.contextual.id ConfigUuid = my.contextual.id|http://192.168.1.113:8080/mockprogram?WSDL The difference is the that the factory PID is missing from the replicated configuration. Jira says this bug was fixed in 2.2.4 but looks like it appears in 2.2.4 and in 2.2.5. Is there a workaround for this? [email protected]
