AEM author over tomcat | Community
Skip to main content
S
Shallu_Rohilla
Level 4
May 19, 2020
Solved

AEM author over tomcat

  • May 19, 2020
  • 2 replies
  • 4094 views

Hi,

I am trying to deploy AEM over Tomcat as app server. However, I have a requirement to add a custom filter class which gets gets called on every request, I have configured this in web.xml and the filter class gets called. However this has dependency on a JAR which I have put in the web-inf/lib folder, however it is not able to find the referenced class and throws class not found exception. I thought of including this a dependency but that can't be done as I need to have an actual project with pom.xml but here I have deployed aem war on Tomcat. Any pointers if someone has tried to access class from an external JAR. Any pointers how this can be done. I tried unzipping the war and checking contents, i have my JAR in lib folder but isnt getting picked.

Any pointers would be appreciated.

Regards,

Shallu

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 leoberliant

It looks like you need to warp your filter as a custom bundle and deploy it to AEM.

Some generic inputs about a bundle project could be found here https://docs.adobe.com/content/help/en/experience-manager-core-components/using/developing/archetype/core.html

2 replies

L
Adobe Employee
leoberliantAdobe EmployeeAccepted solution
Adobe Employee
May 20, 2020

It looks like you need to warp your filter as a custom bundle and deploy it to AEM.

Some generic inputs about a bundle project could be found here https://docs.adobe.com/content/help/en/experience-manager-core-components/using/developing/archetype/core.html

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    May 21, 2020

    As @leoberliant  already pointed out, why don't you deploy your filter into AEM? Otherwise you split up your application into multiple codebases, which barely have any relationship and it's actually much harder to share any information between these two.

      Terms & ConditionsAccessibility statement

      Loading footer...