Well I understand that you are not using touch ui components the issue you are facing is not the compile time issue it’s related to runtime binding or you can say resolving the bundle dependencies for which I think your code package is still looking for some old versions of the added jar or dependen...
For troubleshooting can you try by installing the aem code components packages and then doing your maven build and deploy?
you can also add core components as the dependency. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/core-components-not-resolved/m-p/558474
I believe y...
core components are different then the acs-commons.
https://experienceleague.adobe.com/docs/experience-manager-learn/sites/components/core-components-feature-video-understand.html?lang=ennote that Aem doesn’t support the classic ui components anymore so that might not work in aem 6.5.15
A you check if aem core components are installed on your local aem? Is this maven build is your custom code or you just created a maven arch type project from 41 version and deployed it?
Also, in your case Dispatcher won’t cache the response because there is no file extension in the url.
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/cache-servlet-response/m-p/174263
Thanks for Confirming that you are now able to get the response for your servlet via dispatcher. If you looks the aem dispatcher farm.any in case it might be wknd_farm.any check for something similar inside conf.dispatcher.d/available_farms. So on your site-name_farm.any you can see several sections...
[Tue Nov 28 15:01:00.932313 2023] [dispatcher:debug] [pid 313:tid 139849276103480] [client localhost:33972] Filter rejects: GET /bin/random-number HTTP/1.1
Above log shows that one of filter is rejecting this path. I suspect your filters.any file is not loading in your dispatcher. Changes made on de...