Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330673

Summary: ManagedService don't call update() when new configuration is put in pickup
Product: [RT] Virgo Reporter: Peter Lauri <peterlauri>
Component: unknownAssignee: Chris Frost <eclipse>
Status: CLOSED FIXED QA Contact:
Severity: major    
Priority: P3 CC: eclipse, glyn.normington, k2eric
Version: 2.1.0.RELEASE   
Target Milestone: 3.0.0.M01   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Log when deploying bundle and then configuration
none
Maven project that uses ManagedService none

Description Peter Lauri CLA 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.
Comment 1 Peter Lauri CLA 2010-11-19 10:58:59 EST 
Created attachment 183476 [details]
Log when deploying bundle and then configuration
Comment 2 Peter Lauri CLA 2010-11-19 11:01:01 EST 
Created attachment 183477 [details]
Maven project that uses ManagedService
Comment 3 Peter Lauri CLA 2010-11-20 15:19:48 EST 
Tested on Windows and Linux show same result.
Comment 4 Chris Frost CLA 2010-12-14 11:19:34 EST 
This has been fixed and checked using the recreation steps below. This fix will be available in the next 2.2 milestone M2.
Comment 5 Chris Frost CLA 2010-12-14 11:19:53 EST 
Work pushed