Wrong DS error message when using ServiceFactory

[phermsdorf]

Hi,

i recently tried to replace programmatically registration of ServiceFactory classes by using DS Annotations instead.

Background: instead of registering a concrete implementation for a service there is the possibility to instead register a ServiceFactory for the Service and when a service object is needed ServiceFactory.getService is called. (for more information see please the javadoc of ServiceFactory)

I came up with something like this:

import org.osgi.framework.Bundle;
import org.osgi.framework.ServiceFactory;
import org.osgi.framework.ServiceRegistration;
import org.osgi.service.component.annotations.Activate;
import org.osgi.service.component.annotations.Component;
import org.osgi.service.component.annotations.ServiceScope;

@Component(service = CatalogManager.class, scope = ServiceScope.BUNDLE)
public class SvcFactory implements ServiceFactory<CatalogManager> {

	@Activate
	void onActivate() {
		System.err.println();
	}

	@Override
	public CatalogManager getService(Bundle bundle,
			ServiceRegistration<CatalogManager> registration) {
		return null;
	}

	@Override
	public void ungetService(Bundle bundle, ServiceRegistration<CatalogManager> registration, CatalogManager service) {
		// TODO Auto-generated method stub
	}
}

which basically works as expected. The corresponding .xml file is generated and the SerficeFactory get's called then a CatalogManager service is requested.

The only problem is, that in the Java Editor an error is displayed:

I think that is a wrong error message. What do others think about that?

Thanks for loooking into the issue.

Bye Peter

[laeubi]

I think that is a wrong error message. What do others think about that?

Sadly this is currently not supported see

• [ds] allow a component to implement ServiceFactory / PrototypeServiceFactory osgi/osgi#688

if you find this useful (like me) please leave a comment there so we can have this in DS 1.6 specification and later be supported by PDE as well.

[phermsdorf]

Thanks for the hint. I'll have a look.

Are you saying that that is not working at all? (Because i just hacked something like the above component together and it got called .... i think ...)