AEM Core Content fragment CF picker on the dialog is not working , its throw below error . I am getting 500 error in the browser console for below network call . I am using 2022.9.8722.20220912T101352Z-220800 SDK instance. I am unable to select content fragment models from the DAM
GET /mnt/overlay/dam/cfm/content/cfpicker/picker.html HTTP/1.1] com.adobe.granite.metrics.knownerrors.impl.ErrorLoggingComponentFilter Exception in component: category=CUSTOMER_CODE, resourceType=dam/cfm/components/cfpicker/datasources/children, exceptionType=java.lang.NullPointerException, errorId=CUSTOMER, resource=/mnt/overlay/dam/cfm/content/cfpicker/picker/views/column, exceptionMessage = null
28.04.2023 23:47:42.361 *INFO* [[0:0:0:0:0:0:0:1] [1682722062351] GET /mnt/overlay/dam/cfm/content/cfpicker/picker.html HTTP/1.1] libs.granite.ui.components.coral.foundation.columnview Fallback to non-lookahead datasource
28.04.2023 23:47:42.366 *ERROR* [[0:0:0:0:0:0:0:1] [1682722062351] GET /mnt/overlay/dam/cfm/content/cfpicker/picker.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException
java.lang.NullPointerException: null
at com.adobe.cq.dam.cfm.impl.ui.ListChildrenDatasource.doGet(ListChildrenDatasource.java:81) [com.adobe.dam.cq-dam-cfm-impl:0.12.290]
at org.apache.sling.api.servlets.SlingSafeMethodsServlet.mayService(SlingSafeMethodsServlet.java:266) [org.apache.sling.api:2.27.0]
at org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:342) [org.apache.sling.api:2.27.0]
at org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:374) [org.apache.sling.api:2.27.0]
at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:518) [org.apache.sling.engine:2.12.2]
at org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45) [org.apache.sling.engine:2.12.2]
Solved! Go to Solution.
Views
Replies
Total Likes
@TarunKumar - Thanks for your reply. This issue got resolved now , it was occurring due to custom servlet in our codebase . We fixed it and core CF component cf path picker started working
@TarunKumar - Thanks for your reply. This issue got resolved now , it was occurring due to custom servlet in our codebase . We fixed it and core CF component cf path picker started working
Views
Likes
Replies