Thanks for all your answers.I'm afraid that tutorial above doesn't solve my issue. but indeed the missing link was that the Java class wasn't visible to OSGi because it wasn't in the bundle manifest.To correct that, I had to add the details for all of the imported and exported packages to the org.ap...

Thanks so much for responding, Swati. That's exactly what was missing! I'm so used to using Felix SCR annotations on my bundled classes that I forgot to check whether my use class was being added to the exported-packages manifest. Everything seems to work fine now.Much appreciated! Taylor

I've been trying to get a Sightly component working in AEM 6.1 by following the documentation hereApparently, in order to have my Java "use" class be visible to my Sightly component, all I need to do is use the full Class name (i.e. including the package) in my "use" statement.<div data-sly-use.list...

@swathi07Can you please be more specific about the imports you added to correct this?It doesn't work for me, either. I getting the same exception you were and nothing seems to correct it.My class extends WCMUsePojo and my bundle is pulling in the following dependencies in the pom.xml (for both paren...