AEM 6.3 OSGI Filter Component with satisfied status | Community
Skip to main content
leopor
leopor
Level 2
June 2, 2018
Solved

AEM 6.3 OSGI Filter Component with satisfied status

  • June 2, 2018
  • 9 replies
  • 3934 views

Hi everyone,

I'm trying to implement OSGI Filter Components, I deployed this bundle on my local: GitHub - Adobe-Consulting-Services/acs-aem-samples: AEM Code Samples repository and I'm testing this example: acs-aem-samples/SampleServletFilter.java at master · Adobe-Consulting-Services/acs-aem-samples · GitHub

But when I look for the component in the osgi console I figured out that it has satisfied status.

I also tried to debug, I put a breakpoint inside doFilter method but nothing happens.

I'm testing the bundle on AEM 6.3 clean instance, I not deployed anything else.

Does anyone know what is happening?

Why doesn't the component have active status?

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 smacdonald2008

David stated:

Because its never been invoked; unless its marked as immediate=true, it wont become active (one of the beauties of OSGi)

This is like any other OSGi component and nothing special about this filter.

9 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
June 2, 2018

you are using Felix annotations. Can you try with new OSGI annotations

Using OSGi annotations (>= AEM6.2) - Experience Delivers

Thank

Arun

Arun Patidar
joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 3, 2018

Are you using AEM 6.2 SP2?

Can you open the bundle in the webconsole view and check which dependency is missing?

kind regards,
Jörg

Feike_Visser1
Adobe Employee
Feike_Visser1Adobe Employee
Adobe Employee
June 3, 2018

Indeed, go to the component view in /system/console, there get more detail why the component is 'satisfied'

leopor
leoporAuthor
Level 2
June 4, 2018

I'm using AEM 6.3

This is the bundle info:

leopor
leoporAuthor
Level 2
June 4, 2018

This is the information:

I wasn't able to find a clue.

smacdonald2008
smacdonald2008
Level 10
June 4, 2018

I built this same code from the GitHub Repo...

leopor
leoporAuthor
Level 2
June 4, 2018

Thank you smacdonald for you response.

I did the same, I moved the ResourceResolver to 158 line before I deployed the bundle the first time.

Actually, my problem is not with the bundle

My problem is with the service with this name "SampleSerletFilter" it appears with the satisfied status.

smacdonald Could you check on your local "/system/console/components/" if this SampleServletFilter appears with the same status?

Thank you

smacdonald2008
smacdonald2008
Level 10
June 4, 2018

I am checking with the Consulting team here. I see same result for SampleServletFilter. 

smacdonald2008
smacdonald2008Accepted solution
Level 10
June 4, 2018

David stated:

Because its never been invoked; unless its marked as immediate=true, it wont become active (one of the beauties of OSGi)

This is like any other OSGi component and nothing special about this filter.

    Terms & ConditionsAccessibility statement

    Loading footer...