I am working on an upgrade from AEM 6.2 to AEM 6.5. I am also moving from a very old archetype to the newer archetype 40 with profiles so that the build and deploy may be automated instead of a lot of manual steps that are now being used.I am having problems with the JSP files that include some cust...
So I'll add this in case it helps someone else.Most of the issues were fixe by adding the servlet and service packages to the <Export-Package> section of the POM files.I still would not see errors in the log files when starting the bundles. How I discovered the issues with the remaining servlets tha...
One of my coworkers found an issue with the POM file. It looks like the package for the configuration classes wasn't included in the export list. I could see them in the bundle so I thought they should resolve.
Logs aren't showing what the problem is. No stack traces based on the resolution.It looks like the issue is with the OSGI configuration classes. They are being resolved but not transitioning to the "active" state so I'm sure this is the root issue.Adding log messages to the servlet or the configurat...
The servlet in question, and others, show the state as resolved. If I stop and start the servlet in the components page, there are errors not seen when the bundle starts stating the implementation class cannot be found. When I look at the detail for the bundle that the servlet is part of, I see that...
It is resolved. I don't see any errors in the log other than there is an error when the request comes in for that path.I look in the component list and I can find the servlet listed. Opening the detail, it shows that it is active, the sling.servlet.paths has the path in question listed.Switching to ...
Right now, the request is made when editing pages on my local instance. There is no run mode assignment.This is from old code that was running in 6.2 and the annotations are from the felix project. That shouldn't be the issue because there are other servlets using the same annotations that are resol...
I have a project that has path based several servlets. For some, the path resolves and for some others, not.Using the path in the Sling Servlet Resolver, the path is not resolved to the servlet configured to handle the request.Checking the system/console/components page, I can locate the servlet. Wh...
Though it is true that the classic UI is "disabled"(just not shown), you can add a simple overlay and the link to switch can be added to the drop down menu on the editor page. You can also replace "editor.hml" with cf# in the address bar to switch. It looks like my issue might be that the sling serv...
Well, It looks like something the legacy code is doing. I have an instance I can run on my personal system and I can easily switch to the classic UI by just switching the touch IU's edit.html with cf# in the url and the UI switches seamlessly. Of course there isn't much I can do because I don't have...