AEM 5.6.1 gives error in local instance - The absolute uri: http://www.adobe.com/wem/cq/components cannot be resolved

[Ravi_KS]

Hi All,

Today we downloaded AEM 5.6.1 and installed all our content and application components and then when I click on a page I am getting the mentioned below error

Error Message:

org.apache.sling.api.scripting.ScriptEvaluationException: org.apache.sling.scripting.jsp.jasper.JasperException: /apps/dsm/components/page/head.jsp(1,1) The absolute uri: http://www.adobe.com/wem/cq/components cannot be resolved in either web.xml or the jar files deployed with this application

Processing Info:

We were using 5.5 SP2 earlier and it was fine there the applications I deployed still works fine in 5.5 SP2 version. 

Can someone help me what else we should do to solve this issue in 5.6.1?

[Former Community Member]

        could you please paste the head.jsp file here

[Ravi_KS · Accepted solution]

Found the issue. The dependency of com.day.commons.osgi.wrapper uses FOP 0.95 version of FOP and AEM 5.6.1 uses org.apache.xmlgraphics - FOP of version 1.1 . Hence there was a conflict. Now used 1.1 and removed the wrapper dependency solved the issue.

Cheers,

Ravi

[smacdonald2008]

Thank you for posting the resolution to your issue. It may help future community members. 

[Ravi_KS]

In head.jsp we refer our custom global.jsp and mentioned below is the code in our customised global.jsp

In our global.jsp we have the reference to the http://www.adobe.com/wem/cq/components. Hope this gives you more clarity

<%--
  Copyright 1997-2008 Day Management AG
  Barfuesserplatz 6, 4001 Basel, Switzerland
  All Rights Reserved.

  This software is the confidential and proprietary information of
  Day Management AG, ("Confidential Information"). You shall not
  disclose such Confidential Information and shall use it only in
  accordance with the terms of the license agreement you entered into
  with Day.

  ==============================================================================

  Global WCM script.

  This script can be used by any other script in order to get the default
  tag libs, sling objects and CQ objects defined.

  the following page context attributes are initialized via the <cq:defineObjects/>
  tag:

    @param slingRequest SlingHttpServletRequest
    @param slingResponse SlingHttpServletResponse
    @param resource the current resource
    @param currentNode the current node
    @param log default logger
    @param sling sling script helper

    @param componentContext component context of this request
    @param editContext edit context of this request
    @param properties properties of the addressed resource (aka "localstruct")
    @param pageManager page manager
    @param currentPage containing page addressed by the request (aka "actpage")
    @param resourcePage containing page of the addressed resource (aka "myPage")
    @param pageProperties properties of the containing page
    @param component current CQ5 component
    @param designer designer
    @param currentDesign design of the addressed resource  (aka "actdesign")
    @param resourceDesign design of the addressed resource (aka "myDesign")
    @param currentStyle style of the addressed resource (aka "actstyle")

  ==============================================================================

--%><%@page session="false" import="javax.jcr.*,
        org.apache.sling.api.resource.Resource,
        org.apache.sling.api.resource.ValueMap,
        com.day.cq.commons.inherit.InheritanceValueMap,
        com.day.cq.wcm.commons.WCMUtils,
        com.day.cq.wcm.api.Page,
        com.day.cq.wcm.api.NameConstants,
        com.day.cq.wcm.api.PageManager,
        com.day.cq.wcm.api.designer.Designer,
        com.day.cq.wcm.api.designer.Design,
        com.day.cq.wcm.api.designer.Style,
        com.day.cq.wcm.api.components.ComponentContext,
        com.day.cq.wcm.api.components.EditContext"
%><%@taglib prefix="sling" uri="http://sling.apache.org/taglibs/sling/1.0" %><%
%><%@taglib prefix="cq" uri="http://www.day.com/taglibs/cq/1.0" %><%
%><%@taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %><%
%><%@taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %><%
%><%@taglib prefix="fn" uri="http://java.sun.com/jsp/jstl/functions" %><%
%>

<%@taglib prefix="cmp" uri="http://www.adobe.com/wem/cq/components" %>
<%@taglib prefix="wcmmode" uri="http://www.adobe.com/wem/cq/wcmmode" %>

<cq:defineObjects />

<cq:setContentBundle />

[Paul_McMahon]

I believe those are tag libs from the Adobe Consulting Service AEM commons project - although in the latest versions I believe they changed the URIs. Are you sure you deployed the AEM Commons bundles to you new instances? I'd say there are two possibilities - either the bundles containing those tag libraries haven't been deployed and you need to do that, or they have been deployed but they aren't starting because of dependency versions. You may need to download the latest versions of those bundles and deploy them - in which case you may need to update your URI since I think they changed them to remove the wem references. 

[justin_at_adobe]

Hi,

In general, taglibs in ACS AEM Commons will have namespace URIs starting with "http://www.adobe.com/consulting/acs-aem-commons".

I would generally agree with the potential problems -- either the bundle containing these taglibs isn't deployed or can't be resolved. That bundle just isn't from ACS AEM Commons 

Regards,

Justin

[Ravi_KS]

Hi All,

Today I checked according to your replies. Everything was fine except that our custom bundle was not installed due to an error org.apache.fop.apps,version=[0.95,1) -- Cannot be resolved. I did all to solve this. Even if I change the version to 1.0, in the manifest file I still see reference to the 0.95 version. Do anyone have any idea on how to resolve this. This is creating the problem which I mentioned initially. 

Pls let me know your inputs on this.