In order to manage service factory in a better way, I can implement
something similar to fileinstall: a specific property like
karaf.cellar.factoryPid to know where the factory comes from.
It's the way that fileinstall manage each *.cfg file (adding the
felix.fileinstall.filename property).
Let me dig around that and improve this.
Regards
JB
On 01/22/2015 06:27 PM, Ronny Bräunlich wrote:
Hi everyone,
I am using Apache Karaf 3.0.2 and Cellar 3.0.1-SNAPSHOT (built from
commit 7a598b285f7b302efa15d9887dfea9d855b9951a) and I think I found a bug.
I have two Karaf instances running. On both I installed Cellar and this
simple project
https://github.com/rbraeunlich/karaf-managed-service-factory-example
After setting config.listener = true on both and removing
service.factoryPid from the config.excluded.properties I dropped a
config file into the etc/ directory.
Then I could see the factory on the first Karaf instance getting called
with the properties roughly every 100ms.
Debugging the Karaf couldn’t show me the source of the problem. I
suggest the Karaf updates itself and therefore calls the update() method
all the time.
The second instance didn’t make a move all the time.
Does anyone have a clue?
Cheers,
Ronny
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
