Expand my Community achievements bar.

SOLVED

ProxyAsyncScriptableFactory uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle.

Avatar

Level 2

Hi,

We are getting some warning messages in logs.

 

28.07.2020 01:15:11.225 *WARN* [10.43.32.87 [1595898911218] GET /content/diagnostics/be/en/products/product-category/clinical-chemistry-and-immunochemistry.html HTTP/1.1] org.apache.sling.scripting.sightly.js.impl.jsapi.ProxyAsyncScriptableFactory Script /libs/wcm/foundation/components/page/head.js uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle.

 

Could you please let us know how to resolve this.

we have been upgraded from aem 6.2 to 6.4

is this upgrade issue or we need to update head.js file or any API.

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

This is expected and by default, there is a logger to exclude these kind of warnings from error.log. See below:

 

Screen Shot 2020-07-29 at 11.21.06 AM.png

If similar logger does not exist under /system/console/slinglog. Go ahead and create one and make sure the log level is set to ERROR so that these warnings are not shown in error.log

 

View solution in original post

6 Replies

Avatar

Level 2
Yes i could see..can i know is the issue resolved?

Avatar

Level 2
They have mentioned updated head js file but after no confirmation if that issue resolved..

Avatar

Community Advisor
Can you try using this sling:resourceSuperType /libs/wcm/foundation/components/basicpage/v1/basicpage

Avatar

Correct answer by
Employee Advisor

This is expected and by default, there is a logger to exclude these kind of warnings from error.log. See below:

 

Screen Shot 2020-07-29 at 11.21.06 AM.png

If similar logger does not exist under /system/console/slinglog. Go ahead and create one and make sure the log level is set to ERROR so that these warnings are not shown in error.log