AEM 6.1 Upgrade Issue | Community
Skip to main content
abhishek_09
abhishek_09
New Participant
October 16, 2015
Solved

AEM 6.1 Upgrade Issue

  • October 16, 2015
  • 2 replies
  • 799 views

Hi,

I upgraded my CQ 5.6.1 to AEM 6.1. But there is an error while uploading my custom bundle. Hence status of the bundle is showing as Installed and not Active. The log file shows an error:-

org.osgi.framework.BundleException: Unresolved constraint in bundle com.ceb.webcq-bundle [311]: Unable to resolve 311.0: missing requirement [311.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.social.commons.emailreply)(version>=1.3.0)(!(version>=2.0.0)))
 
Because of this everything is failing i.e. pages, workflows etc. When I see the bundle details from console manager, I see other dependencies too that are not able to resolve. These are:-
  1. com.adobe.cq.social.commons.emailreply,
  2. com.adobe.cq.social.moderation.util.common
  3. com.adobe.cq.social.qna.api
  4. org.openxmlformats.schemas.officeDocument.x2006.extendedProperties

I'm using some of the classes inside these packages in my application and so these are required. I saw the API of AEM 6.1 and found these packages to be no more present. Is there any hotfix required to be installed to resolve this? Please let me know the resolution so that my bundle is installed without error.

 

Thanks.

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 Lokesh_Shivalingaiah

I dont see these packages in 6.1 here [1]. There are quite a few changes in the social component framework. You might have to change your code accordingly. If you find difficult, log a support ticket to get help on this.

[1] http://docs.adobe.com/docs/en/aem/6-1/ref/javadoc/overview-summary.html

2 replies

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
New Participant
October 16, 2015

I dont see these packages in 6.1 here [1]. There are quite a few changes in the social component framework. You might have to change your code accordingly. If you find difficult, log a support ticket to get help on this.

[1] http://docs.adobe.com/docs/en/aem/6-1/ref/javadoc/overview-summary.html

JK_Kendall
JK_Kendall
New Participant
October 16, 2015

Thought I'd just point out...

from http://docs.adobe.com/docs/en/aem/6-1/deploy/communities/upgrade.html

Java APIs

When upgrading from AEM 6.0 social communities to AEM 6.1 Communities be aware that many APIs have been reorganized into different packages.  This should be easily resolved when using an IDE for server-side customization of Communities features.

No JSP Component Templates

The Social Component Framework (SCF) uses the HandlebarsJS (HBS) templating language in place of Java Server Pages (JSP) used prior to AEM 6.0.

In AEM 6.0, the JSP components remained alongside the new HBS framework components in the same location, with the HBS components typically located in subfolders named "hbs".

In AEM 6.1, the JSP components are completely removed.  For Communities, it is recommended to replace all use of JSP components with SCF components.

Hope this helps you and anyone else who looks at this question.

- JK

Terms & ConditionsAccessibility statement

Loading footer...