Exception in using Query Package Manager | Community
Skip to main content
V
vipulp33825167
New Participant
October 16, 2015
Solved

Exception in using Query Package Manager

  • October 16, 2015
  • 2 replies
  • 1107 views

I have acs-aem-commons-content-1.9.4.zip installed  on AEM 6. While creating page using "Query Packager" template [from ACS AEM common], I am getting following exceptions and unable to create page successfully. Any idea what's going wrong here? Appreciate for any solution or pointers :

01.05.2015 21:24:20.109 *ERROR* [0:0:0:0:0:0:0:1 [1430529860036] GET /etc/acs-commons/packagers/contentquerypackager/test2.html HTTP/1.1] org.apache.sling.servlets.resolver.internal.SlingServletResolver Original error class java.lang.Error
java.lang.Error: Unresolved compilation problems: 
    Only a type can be imported. com.adobe.acs.commons.util.TextUtil resolves to a package
    TextUtil cannot be resolved

    at org.apache.jsp.apps.acs_002dcommons.components.utilities.page.page_jsp.<init>(page_jsp.java:22)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at java.lang.Class.newInstance(Unknown Source)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.loadServlet(JspServletWrapper.java:165)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.prepareServlet(JspServletWrapper.java:434)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:486)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:449)
    at org.apache.sling.scripting.jsp.JspScriptEngineFactory.callJsp(JspScriptEngineFactory.java:281)
    at org.apache.sling.scripting.jsp.JspScriptEngineFactory.access$100(JspScriptEngineFactory.java:102)
    at org.apache.sling.scripting.jsp.JspScriptEngineFactory$JspScriptEngine.eval(JspScriptEngineFactory.java:524)
    at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:361)
    at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:171)
    at org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:463)
    at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:511)
    at org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45)
 

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 joerghoh

And in case the problem persists please report this on the github page of ACS. From my experience the support there is excellent.

kind regards,
Jörg

2 replies

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
New Participant
October 16, 2015

Check if all the bundles of acs-aem-commons are in active state.

joerghoh
joerghohAccepted solution
Employee
October 16, 2015

And in case the problem persists please report this on the github page of ACS. From my experience the support there is excellent.

kind regards,
Jörg

Terms & ConditionsAccessibility statement

Loading footer...