I am trying to use the User Picker at
/libs/granite/ui/components/coral/foundation/form/userpicker to select a
user/group in a custom AEM Project wizard.The good news:Predictive
Authorizable look-up worksSelection occurs correctly (e.g. the user ID
is set correctly in the submitted values and saved into the Project)The
not so good news. If I make the field mandatory, validation only works
if:The selection is made with a mouseThe selection is made using
predictive entry (i.e. keyboard), you take ...
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.apache.felix:maven-bundle-plugin entry in the bundle
projects pom.xmlHere's what my pom entry looks
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
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.I've followed the directions and built and deployed my
bundle. My compiled class is in there (I cracked the JAR to make
certain.) and still, the Sightly engine cannot find my class. I've tried
WCMUse and WCMUsePojo. I've t...
@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 parent and child projects):