Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

org,apache.sling.servlet-helpers Bundle is missing in the AEM version 6.5.21 system console

Avatar

Level 1

Hi Team, Initially, the code worked as expected without using the embed property, while running on AMS AEM 6.5 (exact service pack version unknown). We are using the org.apache.sling.servlet-helpers dependency, which is correctly declared in the pom.xml. However, we suddenly encountered an issue with the target sync functionality. Upon debugging, we discovered that the servlet-helpers JAR was missing. The JAR is not visible in the AEM console or listed among the active bundles. To resolve this, we applied the embed property to include the JAR under the /apps folder. Unfortunately, this workaround has led to Sonar issues related to the dependency. We are currently using AEM version 6.5.21. The servlet-helpers JAR is available in AEM as a Cloud Service, but it appears to be missing in AEM 6.5. We're unsure whether it was replaced or bundled within another JAR. Is it acceptable to manually install the JAR via the AEM console under bundles, or is there a recommended way to restore it? Additionally, is there an alternative approach to sync Experience Fragments (XF) to Adobe Target through code without using the dependency? Dependency: ----------------------------- org.apache.sling org.apache.sling.servlet-helpers 1.4.6   org.apache.sling org.apache.sling.servlet-helpers /apps/sample-bundles/install Code: -------------------------------------- InternalRequest req; req= new SlingInternalRequest(resourceResolver, slingProcessor, "http://localhost:6504/libs/cq/experience-fragments/content/commons/targetexporter.html"). withRequestMethod("POST").withParameter("path", xfPath).execute(); Sonar Issues: The product interface org.apache.sling.api.request.RequestParameter annotated with @ProviderType should not be implemented by custom code. Detected in org.apache.sling.servlethelpers.MockRequestParameter contained in /apps/sample-bundles/install/org.apache.sling.servlet-helpers-1.4.6.jar. The product interface org.apache.sling.api.request.RequestParameterMap annotated with @ProviderType should not be implemented by custom code. Detected in org.apache.sling.servlethelpers.MockRequestParameterMap contained in /apps/sample-bundles/install/org.apache.sling.servlet-helpers-1.4.6.jar. Can you please help me on this to resolve the sonar issue or to update the code or to update the JAR in system console. Thanks in Advance. Thanks, Bhanu M.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies

Avatar

Employee

hello @BhanuMa 
Manually installing or embedding this JAR to enable servlet simulation in production may not be the best choice, as it contains mocks that implement Sling interfaces marked with @ProviderType, triggering Sonar violations.
This issue is highlighted in https://issues.apache.org/jira/browse/SLING-12602 which moves such mocks to a test-only jar to prevent their runtime use.
For syncing Experience Fragments to Adobe Target, have you tried using standard HTTP clients to call the exporter endpoint instead?

Avatar

Level 1

Hi @muskaanchandwani ,

 

Thanks for your reply.

 

Is it possible to hit the internal AEM call through HTTPclient. Without doing any some network activity. I need to hit the below libs path to export  

libs/cq/experience-fragments/content/commons/targetexporter.html