Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

How do I access an OSGI service from any class?

jayv25585659
Level 6
Level 6

I have a service (located inside /core/src/java/com/myhost/core/services) and service implementation (located /core/src/java/com/myhost/core/services/impl).

I have an existing class (located inside /core/src/java/com/myhost/core/impl/view/components) that extends com.adobe.cq.sightly.WCMUsePojo. Using getSlingScripterHelper, this class can acceess the service I mentioned above.

I'm trying to access the service without using WCMUsePojo. How can I do it?

Thanks!

1 Accepted Solution
BrijeshYadav
Correct answer by
Level 5
Level 5

What exactly is your use case not to use WCMUsePojo class?

I would recommend to use Sling Model instead of WCMUsePojo.

Adobe Experience Manager Help | Creating Adobe Experience Manager 6.3 Sling Model Components

Sling models and WCMUsePojo

AEM Concepts | AEM Tutorial | Know Adobe CQ better: Sling models and WCMUsePojo

View solution in original post

3 Replies
BrijeshYadav
Correct answer by
Level 5
Level 5

What exactly is your use case not to use WCMUsePojo class?

I would recommend to use Sling Model instead of WCMUsePojo.

Adobe Experience Manager Help | Creating Adobe Experience Manager 6.3 Sling Model Components

Sling models and WCMUsePojo

AEM Concepts | AEM Tutorial | Know Adobe CQ better: Sling models and WCMUsePojo

View solution in original post

smacdonald2008
Level 10
Level 10

When you are in a SLing Model - you can reference another OSGi Serice by using:

@Inject

MyService service ;

This works nicely.

Jörg_Hoh
Employee
Employee

Technically speaking, there is a chance to get the bundlecontext of the bundle, which the class is part of. And from there get references to other services. But that's not easy to implement, and additionally this reference is not managed, thus you need to take care of the lifecycle events of the surrouding services. Probably not what you want.

Instead I would suggest that you convert your custom class into an OSGI service (or Sling model), because then the full tooling is available, and the frameworks takes care about wiring and all other lifecycle events and situations. In my coding experience I also often thought of simple utility classes, and ended up converting them into OSGI services, because then it was much easier to access the services available in the system.