Check out this Adobe Tech Medium blog written by the sole developer who created the Java SDK. This article provides recommendations and best practices on integrating with the Java SDK in a highly-performant fashion and walks through sample code to showcase some of the cool performance enhancements we provide developers out of the box!
Customers's developers can now contribute to the Java SDK as it is open sourced! We recognize the fact that sometimes we can't move as fast as our customers want us to and address feature requests for the SDKs. Therefore, we wanted to open this up to the world so that our SDKs can evolve organically without compromising and slowing down the pace of innovation. We foresee our SDKs evolving in a way that can address really cool use cases in the future.
We have included a change log that will include all future releases and bug fixes. This is important for developers to have access to so that they understand what was added, changed, and deprecated when integrating with our SDK.
I am trying to integrate the Java SDK in my AEM Core bundle and running into a lot of issues with respect to the dependencies.
I am able to get the bundles up and running after converting the regular jar to an osgi bundle but the code that makes the server side call results into a lot of NoClass error. I am afraid I am missing something while converting the jar to an osgi bundle.
The code I am trying to write within an AEM servlet works like charm if i create a Spring boot app so I am quite positive the code I am writing is correct but the dependencies seems like an issue.