Description Peter Lauri 2010-11-19 10:40:23 EST

Build Identifier: virgo-web-server-2.1.0.RELEASE

When using OSGI ManagedService an update() call is expected if a new properties file is put into the pickup directory. However, errors are raised and no call to update() is done.

However, if you would before startup of virgo would put the configuration in the config directory, then all updated works as it should.

I will attach a maven project that can be used to test this.

Reproducible: Always

Steps to Reproduce:
Based on the maven project attached.

1. Start the bundle that registers ManagedService with properties Constants.SERVICE_PID="com.pjotr.managedservicetest"
2. You will get log message "Update count: 1" and "Got update config: null". This is as expected, as no configuration exists.
3. Create com.pjotr.managedservicetest.properties file and then copy it to pickup directory. No update is called, but errors are seen in the log that the configuration is already bound to another bundle.