java.lang.ClassNotFoundException: com.fasterxml.jackson.databind.ser.FilterProvider not found by core bundle | Community
Skip to main content
NageshRaja
Level 5
February 4, 2026
Question

java.lang.ClassNotFoundException: com.fasterxml.jackson.databind.ser.FilterProvider not found by core bundle

  • February 4, 2026
  • 1 reply
  • 14 views

Hi guys,

 

I am getting this issue on all my content pages in the AEM repo - 

04.02.2026 17:11:30.988 *ERROR* [[0:0:0:0:0:0:0:1] [1770205290899] GET /content/projectA/us/en/home.html HTTP/1.1] com.day.cq.wcm.core.impl.WCMDeveloperModeFilter Error during include of SlingRequestPathInfo: path='/content/projectA/us/en/home/jcr:content', selectorString='null', extension='html', suffix='null'
java.lang.NoClassDefFoundError: com/fasterxml/jackson/databind/ser/FilterProvider

Caused by: java.lang.ClassNotFoundException: com.fasterxml.jackson.databind.ser.FilterProvider not found by aem-projA.core [622]
    at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)

 

I do have the bundle “jackson-databindcom.fasterxml.jackson.core.jackson-databind”

It is exporting the package com.fasterxml.jackson.databind.ser,version=2.17.2

Though the error is for ser.FilterProvider I don’t see it in the codebase.

    1 reply

    giuseppebaglio
    Level 10
    February 4, 2026

    Hi ​@NageshRaja,

    FilterProvider lives inside the jackson-databind jar, not inside your project sources. The fact that you do not see it in your own code is normal. The error means:

    • Some code in aem-projA.core (your code or a library your bundle uses) references that class.
    • OSGi cannot resolve it because the bundle that uses it is not properly wired to the bundle that exports it.


    Since you’ve ensudered AEM exports com.fasterxml.jackson.databind.ser with version 2.17.2, in your core/pom.xml make sure jackson-databind is a provided dependency so the bnd plugin can see the package:

    <dependency>
      <groupId>com.fasterxml.jackson.core</groupId>
      <artifactId>jackson-databind</artifactId>
      <version>2.17.2</version> // to match with version in AEM
      <scope>provided</scope>
    </dependency>

     

    NageshRaja
    Level 5
    February 4, 2026

    Hi ​@giuseppebaglio, thank you for the reply!
    Yes the dependency is already configured correctly as you mentioned above. 

    giuseppebaglio
    Level 10
    February 4, 2026

    Have you reviewed the stack trace to identify which class in your project is causing the exception? Could this be related to a misconfiguration in Jackson?