"Steven E. Harris" <[EMAIL PROTECTED]> writes: > In another bundle, I use the ConfigurationAdmin service to create a > new factory configuration using "mycorp.foo_factory" as the > PID. However, I never see my mycorp.Foo class constructor get > called.
It turns out the problem was my use of the single-argument form of ConfigurationAdmin.createFactoryConfiguration(), which binds the Configuration to the current bundle. As the ManagedServiceFactory I was looking to configure is registered by a different bundle, the Configuration was not getting "bound" by DS, per the DS specification. Using the two-argument createFactoryConfiguration(), passing null as the location, works just fine -- provided the configuring bundle has the proper permission. -- Steven E. Harris
