That did not resolve the issue. Looking at the versions of bundles, I can't explain how it works in the 6.2 environment because of class inheritance. Changing versions only changed where the class cast or class not found exceptions were encountered. It was easier to refactor the code so that it work...

I gave up on trying to figure out why it was working in 6.2 but not 6.5 and just refactored the code so that it works. I find it interesting that in the 1.3.1 version of com.thoughtworks.xstream bundle, the EncodedByteArrayConverter does not extend the SingleValueConverter but 1.4.9 does. In 6.2 the...

So we are finally migrating from 6.2 to 6.5 and there is an issue I'm running into with the at org.xmlpull.v1.XmlPullParserFactory class. I am seeing the following error in 6.5 but it works fine in 6.2.Caused by: org.xmlpull.v1.XmlPullParserException: caused by: org.xmlpull.v1.XmlPullParserException...

Thank you for the reply. I really only needed to verify the location where the bundles are stored. It looks to be the same as the 6.5 version that I am very familiar with.

I have to support some legacy 6.2 systems. Yes I know we should be running the latest 6.5 version. We have a side project to do this but until we have those systems fully integrated to some systems, I still have to maintain the legacy 6.2 systems.We had one instance get corrupted on us and rebuilt a...

I resolved this by removing dependencies and changing some servlet annotations so they did not use the @componentannotation from the osgi packages.

No I did not find any of the responses as all that helpful. Many were goose chases that wasted my time.

Last I looked, there wasn't a 6.5.15 uber-jar. We are using the 6.5.0 version. The dependency viewer is no help. There isn't a package named osgi.component. This has something to do with the ogsi.extender somehow. 

Some dependencies are older versions because of the back end code. Which dependency should I be looking at to resolve this? If you have an idea which dependencies I need to look at, that would help. The problem I'm having is that I don't know which one is causing the issue.

I think people are a little confused. Our code uses none of the core components in AEM 6.5. They are all classic UI based so I see no point in chasing down core component dependencies. There are none.I am fully aware that the classic UI is deprecated and not supported. That being said, if you really...