Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Adobe Summit 2023 [19th to 23rd March, Las Vegas and Virtual] | Complete AEM Session & Lab list
SOLVED

AEM 6.5 form custom submit not resolving my service

Avatar

Level 2

I am trying to create custom submit action and calling my service from from post.POST.jsp similar to below but calling my service inplace of mail.

https://docs.adobe.com/content/help/en/experience-manager-65/forms/customize-aem-forms/custom-submit...

 

way i am calling.  

core.service.HandleContactForm hf = sling.getService(core.service.HandleContactForm.class);

 

bundle is active but its not resolving service.

Error is : core.service.HandleContactForm cannot be resolved to a type 

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi @amitcsknit ,

 

Can you please confirm if all other bundles are in "active" state. Specifically, check for AEMFD Signature bundle & AEM RM Indexer Bundle. 

 

Similar issue, I also faced at my end and it automatically resolved after making these two bundles in the "active" state by adding below properties in sling.properties

sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.*
sling.bootdelegation.class.org.bouncycastle.jce.provider.BouncyCastleProvider=org.bouncycastle.*
 
Let me know if that makes any difference.
 
Regards
Sameer Dhawan
4 Replies

Avatar

Level 1

Hi @amitcsknit , Could you please check on following things-

  1. Check if your service is in satisfy state in bundle.
  2. Import service and try using: HandleContactForm hf = sling.getService(HandleContactForm .class);
  3. Check error log for full stack trace of error.
  4. Try using SlingScriptHelper instead of sling to call service from jsp.

Hope this will help you out.

 

Thanks!

Avatar

Correct answer by
Employee

Hi @amitcsknit ,

 

Can you please confirm if all other bundles are in "active" state. Specifically, check for AEMFD Signature bundle & AEM RM Indexer Bundle. 

 

Similar issue, I also faced at my end and it automatically resolved after making these two bundles in the "active" state by adding below properties in sling.properties

sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.*
sling.bootdelegation.class.org.bouncycastle.jce.provider.BouncyCastleProvider=org.bouncycastle.*
 
Let me know if that makes any difference.
 
Regards
Sameer Dhawan

Avatar

Level 2

bundle was active but still This was not happening because custom package was not in export list inside manifest. For testing i moved my classes to model or any preexisting package & they are getting resolved.  Now question came why it is not in export inside manifest.