ConfigurationManager Reference is null | Community
Skip to main content
B
bhavani_ikkurth
Level 2
October 16, 2015
Solved

ConfigurationManager Reference is null

  • October 16, 2015
  • 13 replies
  • 3519 views
import com.day.cq.wcm.webservicesupport.Configuration; import com.day.cq.wcm.webservicesupport.ConfigurationManager; @Component(immediate=true) public class Videos { private final Logger log = Logger.getLogger(Videos.class); private Configuration configuration; @Reference private ConfigurationManager cfgMgr; public void connectToService() { configuration = cfgMgr.getConfiguration("mycustomservice"); } }

 

cfgMgr is null. I wonder why is a reference variable null anyway. Are there any other methods to get it? Any help is appreciated. Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JustinEd3

The problem doesn't have anything to do with this class. It has to do with how you are accessing this class or really the instance. You are creating a new instance of this class. Instead, you should use the instance created by DS.

You should not use getServiceReference() in a DS component except for very specific needs (which this is definitely not an example of).

13 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

Looks right to me. Are you sure cfgMgr is null OR calling configuration cfgMgr.getConfiguration("mycustomservice") is null.

B
bhavani_ikkurthAuthor
Level 2
October 16, 2015

I am sure cfgMgr is null. I added a null check statement to find it out and it came out as null. Do you think I ran into any kind of bug here?

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

That is a possibility - when you inject a ConfigurationManager - it should not be null. Sham - do you think a ticket should be opened?

B
bhavani_ikkurthAuthor
Level 2
October 16, 2015

smacdonald2008 wrote...

That is a possibility - when you inject a ConfigurationManager - it should not be null. Sham - do you think a ticket should be opened?

 

So, is there another way of getting the ConfigurationManager without using Reference annotation? Please advise.

Sham_HC
Sham_HC
Level 10
October 16, 2015

It is not a bug & I can'ot reproduce the issue. Which version of AEM?  Are you seeing the configuration manager in your instance at http://localhost:4502/system/console/services

Otherway of getting is using bundlecontext getService method.

B
bhavani_ikkurthAuthor
Level 2
October 16, 2015

Sham HC wrote...

It is not a bug & I can'ot reproduce the issue. Which version of AEM?  Are you seeing the configuration manager in your instance at http://localhost:4502/system/console/services

Otherway of getting is using bundlecontext getService method.

 

I am on CQ 5.5 I can see the service. 

[img]Screen Shot 2013-10-10 at 3.38.46 PM.png[/img]

B
bhavani_ikkurthAuthor
Level 2
October 16, 2015

Do I have to add the package cq-wcm-webservice-support as an exclusive dependency to the maven pom.xml? Can you please provide me a code snippet to retrieve the service from BundleContext?

B
bhavani_ikkurthAuthor
Level 2
October 16, 2015
protected void activate(ComponentContext context) { BundleContext bundleContext = context.getBundleContext(); ServiceReference serviceReference = bundleContext.getServiceReference(ConfigurationManager.class.getName( )); ConfigurationManager cfgMgr = (ConfigurationManager) bundleContext.getService(serviceReference); }

 

 

In the above code also, I get cfgMgr as null. Sham, Can you please share the code that you have tested with?

J
Adobe Employee
JustinEd3Adobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

The problem doesn't have anything to do with this class. It has to do with how you are accessing this class or really the instance. You are creating a new instance of this class. Instead, you should use the instance created by DS.

You should not use getServiceReference() in a DS component except for very specific needs (which this is definitely not an example of).

B
bhavani_ikkurthAuthor
Level 2
October 16, 2015

justin_at_adobe wrote...

The problem doesn't have anything to do with this class. It has to do with how you are accessing this class or really the instance. You are creating a new instance of this class. Instead, you should use the instance created by DS.

You should not use getServiceReference() in a DS component except for very specific needs (which this is definitely not an example of).

 

Well, if I access the DS instance of the class using @Reference annotation it returns null.

Show more replies
Terms & ConditionsAccessibility statement

Loading footer...