Get sling service using ECMA script. Workflow goto step. | Community
Skip to main content
S
subsul1
Level 2
May 1, 2022
Solved

Get sling service using ECMA script. Workflow goto step.

  • May 1, 2022
  • 1 reply
  • 1449 views

I've got a workflow GOTO process step and the below ECMA script as the routing expression. 

 

function check() { log.info("Inside script to fetch enabled flag"); var service = sling.getService(Packages.com.adobe.service.TrialServiceInterface); if (service && service.isEnabled()) { return true } return false; }

 

 

Component and Service Code:

TrialServiceInterface is service interface which is implemented by a component as follow.

 

public interface TrialServiceInterface { ---- boolean isEnabled(); }

 

 

 

@8220494(immediate = true, service = TrialServiceInterface.class) @Designate(ocd = TrialServiceInterfaceConfig.class) public class TrialServiceInterfaceImpl implements TrialServiceInterface { ---- --- public boolean isEnabled() { LOGGER.debug("Call from ECMA script"); return enabled; } }

 

 

Exception:

 

30.04.2022 21:58:34.402 *INFO* [JobHandler: /var/workflow/instances/server0/2022-04-30_1/asset-post-processing_3:/content/dam/content/brands/bbasic_BR_201216.png] libs.workflow.scripts.dynamic$ecma Inside script to fetch enabled flag 30.04.2022 21:58:34.412 *ERROR* [JobHandler: /var/workflow/instances/server0/2022-04-30_1/asset-post-processing_3:/content/dam/content/brands/bbasic_BR_201216.png] com.adobe.granite.workflow.core.rule.ScriptingRuleEngine Unable to execute rule function check() { log.info("Inside script to fetch enabled flag"); var service = sling.getService(Packages.com.adobe.service.TrialServiceInterface); if (service && service.isEnabled()) { return true } return false; } : Failure running script /libs/workflow/scripts/dynamic.ecma: Can't find method org.apache.sling.scripting.core.impl.InternalScriptHelper.getService(object). (NO_SCRIPT_NAME#3) org.apache.sling.api.scripting.ScriptEvaluationException: Failure running script /libs/workflow/scripts/dynamic.ecma: Can't find method org.apache.sling.scripting.core.impl.InternalScriptHelper.getService(object). (NO_SCRIPT_NAME#3) at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:423) [org.apache.sling.scripting.core:2.4.6] at org.mozilla.javascript.DefaultErrorReporter.runtimeError(DefaultErrorReporter.java:77) at org.mozilla.javascript.Context.reportRuntimeError(Context.java:954)

 

 

Environment: AEM as cloud service

According to these docs sling is one of objects available within ECMA scripts.

AEM gurus, any idea why i'm running into this can't find method exception, pls advice?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by lukasz-m

Hi @subsul1,

I was able to reproduce the issue you have described. I think I have also find what is the root cause and solution.

The implementation itself look fine. However there is one small details that could be problematic.

Could you please make sure your interface and class are in java pages that are exported by your bundle. In other words it needs to be exposed to be consumed by other services outside your bundle.

You can verify above very easy. Just go to /system/console/bundles find your bundle and check it details, especially Exported Packages section.

Adding package to be exported solved issue in my local instance.

Depending which plugin you are using below links could be useful:

So in general the error shown in the logs could more descriptive and is not helping in the investigation. Nevertheless I hope this will solve your problem.

1 reply

lukasz-m
Community Advisor
lukasz-mCommunity AdvisorAccepted solution
Community Advisor
May 1, 2022

Hi @subsul1,

I was able to reproduce the issue you have described. I think I have also find what is the root cause and solution.

The implementation itself look fine. However there is one small details that could be problematic.

Could you please make sure your interface and class are in java pages that are exported by your bundle. In other words it needs to be exposed to be consumed by other services outside your bundle.

You can verify above very easy. Just go to /system/console/bundles find your bundle and check it details, especially Exported Packages section.

Adding package to be exported solved issue in my local instance.

Depending which plugin you are using below links could be useful:

So in general the error shown in the logs could more descriptive and is not helping in the investigation. Nevertheless I hope this will solve your problem.

    S
    subsul1Author
    Level 2
    May 1, 2022

    Hi @lukasz-m 

    Many thanks for your time and effort. That too on a Sunday 🙂

    Exporting both the service and the component has resolved the issue.

     

    For those stumbling upon the same problem, here is a ref for Export-Package usage using bnd-maven-plugin

    https://wcm-io.atlassian.net/wiki/spaces/WCMIO/pages/1267040260/How+to+switch+from+maven-bundle-plugin+to+bnd-maven-plugin#Step-5%3A-Verify-Package-Exports

     

    Regards,

    Sub

      Terms & ConditionsAccessibility statement

      Loading footer...