error Handler | Community
Skip to main content
A
avalers
Level 3
October 16, 2015
Solved

error Handler

  • October 16, 2015
  • 11 replies
  • 2481 views

I'm working with handler. I'm trying to use the slingRepository.  However, when I added to my class It's not deploying my handler and its not showing any error.

Any idea?

@Component(
        metatype = true,
        immediate = false
)
@Service
public class MyAuthenticationHandler extends DefaultAuthenticationFeedbackHandler implements AuthenticationHandler {

        
@Reference
 

private SlingRepository slingRepository;

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 Premkarthic-7WP

Avalers,

As a workaround you can get the service reference for sling repository inside activate method using component context as shown below.

@Service
public class TestAuthHandler extends DefaultAuthenticationFeedbackHandler implements AuthenticationHandler
{


    private SlingRepository repo;

    protected void activate(ComponentContext context) {
    
     try {

           BundleContext bundleContext = FrameworkUtil.getBundle(TestAuthHandler.class).getBundleContext();
           ServiceReference factoryRef = bundleContext.getServiceReference(SlingRepository.class.getName());
           repo = (SlingRepository) bundleContext.getService(factoryRef);


        } catch (Exception e) {
            
        }
        
    
        }.........

 

Hope this will work fine for you. Tested on 5.5/6.0. 

Note : I also faced the same issue some long time back when i tried to use sling repository reference inside service. Still debugging on that.

Thanks,

Karthi

11 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

Is component activated?

Premkarthic-7WP
Premkarthic-7WPAccepted solution
Level 4
October 16, 2015

Avalers,

As a workaround you can get the service reference for sling repository inside activate method using component context as shown below.

@Service
public class TestAuthHandler extends DefaultAuthenticationFeedbackHandler implements AuthenticationHandler
{


    private SlingRepository repo;

    protected void activate(ComponentContext context) {
    
     try {

           BundleContext bundleContext = FrameworkUtil.getBundle(TestAuthHandler.class).getBundleContext();
           ServiceReference factoryRef = bundleContext.getServiceReference(SlingRepository.class.getName());
           repo = (SlingRepository) bundleContext.getService(factoryRef);


        } catch (Exception e) {
            
        }
        
    
        }.........

 

Hope this will work fine for you. Tested on 5.5/6.0. 

Note : I also faced the same issue some long time back when i tried to use sling repository reference inside service. Still debugging on that.

Thanks,

Karthi

A
avalersAuthor
Level 3
October 16, 2015

When I added the slingRepository, the service its not longer activated.

A
avalersAuthor
Level 3
October 16, 2015

Thanks for the example. I tried, However, the   factoryref is returning null. 

         ServiceReference factoryRef = bundleContext.getServiceReference(SlingRepository.class.getName());

J
Adobe Employee
JustinEd3Adobe Employee
Adobe Employee
October 16, 2015

Hi,

First of all, never call FrameworkUtil.getBundle() in a component's activate method. You have access to the BundleContext via the ComponenContext. You should actually try to avoid using FrameworkUtil.getBundle() in general as it isn't very performant.

As to the original post, I would suggest looking at the log files and see if there is anything interesting there. It is hard to say what could be causing this for sure; one possibility is that you are embedding the SlingRespository class into your bundle. That would make the service not assignable because the service does not implement the target interface (it implements an interface with the same name but not actually the same interface because they come from different class loaders). Calling getServiceReference() from the activate method may or may not work (although if the service class isn't assignable, it will similarly not work) depending upon the activation order. This is why using DS is preferable to directly accessing the service registry - you don't have to deal with a null result from getServiceReference().

Justin

A
avalersAuthor
Level 3
October 16, 2015

justin_at_adobe wrote...

Hi,

First of all, never call FrameworkUtil.getBundle() in a component's activate method. You have access to the BundleContext via the ComponenContext. You should actually try to avoid using FrameworkUtil.getBundle() in general as it isn't very performant.

As to the original post, I would suggest looking at the log files and see if there is anything interesting there. It is hard to say what could be causing this for sure; one possibility is that you are embedding the SlingRespository class into your bundle. That would make the service not assignable because the service does not implement the target interface (it implements an interface with the same name but not actually the same interface because they come from different class loaders). Calling getServiceReference() from the activate method may or may not work (although if the service class isn't assignable, it will similarly not work) depending upon the activation order. This is why using DS is preferable to directly accessing the service registry - you don't have to deal with a null result from getServiceReference().

Justin

 

I do not have any error in my logs. :S

J
Adobe Employee
JustinEd3Adobe Employee
Adobe Employee
October 16, 2015

avalers wrote...

justin_at_adobe wrote...

Hi,

First of all, never call FrameworkUtil.getBundle() in a component's activate method. You have access to the BundleContext via the ComponenContext. You should actually try to avoid using FrameworkUtil.getBundle() in general as it isn't very performant.

As to the original post, I would suggest looking at the log files and see if there is anything interesting there. It is hard to say what could be causing this for sure; one possibility is that you are embedding the SlingRespository class into your bundle. That would make the service not assignable because the service does not implement the target interface (it implements an interface with the same name but not actually the same interface because they come from different class loaders). Calling getServiceReference() from the activate method may or may not work (although if the service class isn't assignable, it will similarly not work) depending upon the activation order. This is why using DS is preferable to directly accessing the service registry - you don't have to deal with a null result from getServiceReference().

Justin

 

I do not have any error in my logs. :S

 

In that case, I'd suggest looking at the classloader issue I mentioned.

A
avalersAuthor
Level 3
October 16, 2015

justin_at_adobe wrote...

avalers wrote...

justin_at_adobe wrote...

Hi,

First of all, never call FrameworkUtil.getBundle() in a component's activate method. You have access to the BundleContext via the ComponenContext. You should actually try to avoid using FrameworkUtil.getBundle() in general as it isn't very performant.

As to the original post, I would suggest looking at the log files and see if there is anything interesting there. It is hard to say what could be causing this for sure; one possibility is that you are embedding the SlingRespository class into your bundle. That would make the service not assignable because the service does not implement the target interface (it implements an interface with the same name but not actually the same interface because they come from different class loaders). Calling getServiceReference() from the activate method may or may not work (although if the service class isn't assignable, it will similarly not work) depending upon the activation order. This is why using DS is preferable to directly accessing the service registry - you don't have to deal with a null result from getServiceReference().

Justin

 

I do not have any error in my logs. :S

 

In that case, I'd suggest looking at the classloader issue I mentioned.

 

I couldn't find the problem. 

This is my pom:

 

    <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.api</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.auth.core</artifactId>
            <scope>provided</scope>
        </dependency>

A
avalersAuthor
Level 3
October 16, 2015

avalers wrote...

justin_at_adobe wrote...

avalers wrote...

justin_at_adobe wrote...

Hi,

First of all, never call FrameworkUtil.getBundle() in a component's activate method. You have access to the BundleContext via the ComponenContext. You should actually try to avoid using FrameworkUtil.getBundle() in general as it isn't very performant.

As to the original post, I would suggest looking at the log files and see if there is anything interesting there. It is hard to say what could be causing this for sure; one possibility is that you are embedding the SlingRespository class into your bundle. That would make the service not assignable because the service does not implement the target interface (it implements an interface with the same name but not actually the same interface because they come from different class loaders). Calling getServiceReference() from the activate method may or may not work (although if the service class isn't assignable, it will similarly not work) depending upon the activation order. This is why using DS is preferable to directly accessing the service registry - you don't have to deal with a null result from getServiceReference().

Justin

 

I do not have any error in my logs. :S

 

In that case, I'd suggest looking at the classloader issue I mentioned.

 

I couldn't find the problem. 

This is my pom:

 

    <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.api</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.auth.core</artifactId>
            <scope>provided</scope>
        </dependency>

 

Could you give me some directions?

J
Adobe Employee
JustinEd3Adobe Employee
Adobe Employee
October 16, 2015

Perhaps post the whole pom?

Show more replies
Terms & ConditionsAccessibility statement

Loading footer...