Bug 336578 - Managed service factory config callback not firing on Equinox startup
Summary: Managed service factory config callback not firing on Equinox startup
Status: CLOSED WONTFIX
Alias: None
Product: Gemini.Blueprint
Classification: RT
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2011-02-07 21:16 EST by Greg CLA
Modified: 2016-04-28 07:50 EDT (History)
3 users (show)

See Also:


Attachments
Blueprint XML (863 bytes, application/xml)
2011-02-07 21:17 EST, Greg CLA
no flags Details
Managed service factory bean (356 bytes, application/octet-stream)
2011-02-07 21:19 EST, Greg CLA
no flags Details
Equinox/Blueprint/Managed service factory startup trace logs (269.38 KB, text/plain)
2011-02-07 21:28 EST, Greg CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Greg CLA 2011-02-07 21:16:03 EST
Build Identifier: STS build 2.5.2 build 201101081000 / Gemini Blueprint 1.0.0/M1/Equinox 3.6.1

With a managed service factory defined with several configuration keys/values in Equinox, the only time I can get the update-method callback to fire on my bean is when I add or modify a configuration key/value pair after Equinox is started. I would expect the update-method callback to fire when Equinox starts, just like it does for managed-properties on a managed service.


Reproducible: Always

Steps to Reproduce:
1. Configure managed service factory instance in Blueprint xml
2. Create managed service factory config admin instance in Equinox
3. Add a key/value pair to config instance
4. Restart Equinox and observe that config dictionary will not be injected into the bean on startup
Comment 1 Greg CLA 2011-02-07 21:17:56 EST
Created attachment 188489 [details]
Blueprint XML

Blueprint XML with managed service factory
Comment 2 Greg CLA 2011-02-07 21:19:16 EST
Created attachment 188490 [details]
Managed service factory bean

Managed service factory bean with public "update" method to receive config admin injection
Comment 3 Greg CLA 2011-02-07 21:23:06 EST
osgi> cm getv testfactory-1297050867612-0

Configuration for service (pid) "testfactory-1297050867612-0"
(bundle location = reference:file:/Users/grapp/Documents/workspace-sts/TestPlugin/)

key                  value                             type
------               ------                            ------
key1                 value1                            java.lang.String
service.factoryPid   testfactory                       java.lang.String
service.pid          testfactory-1297050867612-0       java.lang.String
Comment 4 Greg CLA 2011-02-07 21:28:02 EST
Created attachment 188491 [details]
Equinox/Blueprint/Managed service factory startup trace logs
Comment 5 Nobody - feel free to take it CLA 2012-11-19 06:22:36 EST
(In reply to comment #0)
> Build Identifier: STS build 2.5.2 build 201101081000 / Gemini Blueprint
> 1.0.0/M1/Equinox 3.6.1
> 
> With a managed service factory defined with several configuration
> keys/values in Equinox, the only time I can get the update-method callback
> to fire on my bean is when I add or modify a configuration key/value pair
> after Equinox is started. I would expect the update-method callback to fire
> when Equinox starts, just like it does for managed-properties on a managed
> service.

I agree the function you describe would be desirable. Unfortunately, Gemini Blueprint does not currently implement that function, so I'm afraid I'll have to classify this as an enhancement rather than a bug.

I will add the 'helpwanted' keyword as it would be great if someone had the time to develop a patch for the new function.
Comment 6 Olaf Kaiser-Otto CLA 2016-04-28 07:50:22 EDT
There has not been any activity on this ticket for a long time. I'll close this as won't fix. To be re-opened if a requirement arises.