{"id":4384795,"date":"2021-04-01T13:12:02","date_gmt":"2021-04-01T11:12:02","guid":{"rendered":"https:\/\/www.deptagency.com\/insight\/binding-and-unbinding-osgi-services-in-aem\/"},"modified":"2025-12-08T13:47:51","modified_gmt":"2025-12-08T11:47:51","slug":"binding-and-unbinding-osgi-services-in-aem","status":"publish","type":"article","link":"https:\/\/www.deptagency.com\/en-in\/insight\/binding-and-unbinding-osgi-services-in-aem\/","title":{"rendered":"Binding and unbinding OSGI services in AEM"},"content":{"rendered":"
\n\t\n\t<\/svg>\n\t\t\t\n\t\t\tBack to all articles\t\t<\/span>\n\t\n<\/button>\n\t\tBinding and unbinding OSGI services in AEM\t<\/h1>\n\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t<\/picture>\n\t\n\t<\/div>
\n\t\t\t\n\t\n\t
\n\t\tHimanshu Mody\t\t
\n\t\tVP Global Adobe Alliances\n\t\t\t<\/div>\n<\/div>\n\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\tDate\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t1 April 2021\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t\t<\/div>\n<\/div>\n\n
\n\t
\n\t\t\n\t\t\t\t\t
\n\t\t\t\t\n\n\t\tIn Adobe\u2019s Experience Manager we have the ability to create OSGi components and services using only Java classes and Src annotations. This is one of AEM\u2019s most powerful features that Java developers can leverage in order to achieve customization. We often create our own components that consume core services that are provided by AEM. Consuming these services can be done very efficiently using references.\t<\/h2>\n\n\n\t\tJust like Spring framework and Google\u2019s Guice it is possible to use dependency injection in AEM in order to acquire a reference to one or more services. The possibilities for this that are offered to us by the OSGi standards are quite numerous, in this blog I\u2019d like to share the basics of using service references with you.\t<\/p>\n\n\n\t\tFirst, to create an OSGi component, simply use the @Component annotation on your class:
@Component
public class MyComponent\t<\/p>\n\n\n\t\tYour newly created component will not be activated automatically when it is not referenced by any other component. This is called delayed activation. To prevent delayed activation you can set the value of \u201cimmediate\u201d in the component annotation to true.
@Component(immediate=true)\t<\/p>\n\n\n\t\tReferencing another component can be done though the usage of the reference annotation:
@Reference
private MyService myService;\t<\/p>\n\n\n\t\tInterfaces for OSGI services\t<\/h2>\n\n\n\t\tWhen using references you\u2019ll need to add the service annotation to your component. You\u2019ll also need to provide a service interface. Providing a service interface is not only good practice but also necessary for the binding process to work correctly. A service that may be referenced would look like this:\t<\/p>\n\n\n\t\t@Component
@Service
public class MyServiceImpl implements MyService\t<\/p>\n\n\n\t\tIn this case the component implementation class is called MyServiceImpl, it\u2019s interface is called MyService. The @Reference annotation will cause a lookup of a service with this exact interface name.\t<\/p>\n\n\n\t\tWhen your OSGi service implementation uses more than one interface each of these can be used to reference the service. You may also specify exactly which interfaces are used:
@Service(value={MyService.class, OtherInteface.class}\t<\/p>\n\n\n\t\tTargeting a service implementation\t<\/h2>\n\n\n\t\tReferencing services using just the reference annotation and nothing more works perfectly for cases in which a service interface has only one implementation. But if a service has multiple implementations you can select a specific implementation by using a property filter:\t<\/p>\n\n\n\t\t@Reference(target = \u201d(type=http)\u201d)
private MyService myService\t<\/p>\n\n\n\t\tThis will make sure that the service implementation that has the property \u201ctype\u201d set to \u201chttp\u201d will be referenced:\t<\/p>\n\n\n\t\t@Component @Service @Properties( @Property(name = \u201ctype\u201d, value = \u201chttp\u201d) ) public class MyServiceImpl implements MyService\t<\/p>\n\n\n\t\tReferences in a list or map\t<\/h2>\n\n\n\t\tIf you have more than one implementation of a service you may want to reference all of them in a list or map. By setting and implementing the bind and unbind methods you can store multiple references of the same service:\t<\/p>\n\n\n\t\t@Reference( referenceInterface = MyService.class, policy = ReferencePolicy.DYNAMIC, cardinality = ReferenceCardinality.MANDATORY_MULTIPLE, bind = \u201cbindMyService\u201d, unbind = \u201cunbindMyService\u201d) private Map<String, MyService> myServiceMap = new HashMap<String, MyService& protected void bindMyService(MyService myService, Map properties) { if (properties.containsKey(\u201ctype\u201d)) { String type = properties.get(\u201ctype\u201d).toString(); myServiceMap.put(type, myService); } } protected void unbindMyService(MyService myService) { myServiceMap.values().remove(myService); }\t<\/p>\n\n\n\t\tNotice that in the reference annotation the attribute \u201creferenceInterface\u201d has been set to the interface class. This is needed because we are now using the Map interface rather than the MyService interface for our class attribute.\t<\/p>\n\n\n\t\tNotice that in the bind method the first argument is a service implementation and the second argument is a map containing the properties of this implementation. This map will contain the property \u201ctype\u201d and the value that has been assigned to it.\t<\/p>\n\n\n\t\tThis setup will allow us to programmatically select one of the referenced services:
public void performAction(String type) { myServiceMap(type).action(); }\t<\/p>\n\t\t\t<\/div>\n\t\t\t<\/div>\n\n\t\n\t