We have an AEM service that needs to integrate with an azure keystore. The Azure java libraries aren't OSGI packages and I haven't been able to get them to work wrapping them myself, likely because their dependency tree is just huge. Anyone else been down this road before and can they offer any advice?
Hi @ben_hp,
In the majority of instances involving third-party bundles, the resolution of the Maven dependency in both the main pom.xml and the core pom.xml results in the successful inclusion of the required bundle.
Nevertheless, there are situations where this automatic process does not occur as expected. In such scenarios, it becomes necessary to prepare the dependency for OSGi compatibility and then embed it into the system.
To accomplish this, you can refer to the instructions provided in the documentation.
https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.html
For detailed changes and procedures, you can refer to this GitHub commit: https://github.com/Sady-Rifat/aem-demo/commit/65f8ce112744134728bf2f85d7bc5f131a2ef290
Same problem is being discussed here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/including-third-party-bundles-in-aem/m-p/611006
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
