Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Binding issue with osgi.component not being resolved

Avatar

Level 4

I am working on an update from a very old archetype to a newer AEM Archetype version 41 and I am having a binding issue after the bundle is deployed to the localhost instance.

The error I'm seeing when I attempt to start the bundle is as follows:

29.11.2023 09:19:09.646 *ERROR* [qtp693971857-5631] org.apache.felix.http.jetty Bundles: Cannot start (org.osgi.framework.BundleException: Unable to resolve wcm-service-facade-core [1348](R 1348.27): missing requirement [wcm-service-facade-core [1348](R 1348.27)] osgi.extender; (&(osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2.0.0))) Unresolved requirements: [[wcm-service-facade-core [1348](R 1348.27)] osgi.extender; (&(osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2.0.0)))])
org.osgi.framework.BundleException: Unable to resolve wcm-service-facade-core [1348](R 1348.27): missing requirement [wcm-service-facade-core [1348](R 1348.27)] osgi.extender; (&(osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2.0.0))) Unresolved requirements: [[wcm-service-facade-core [1348](R 1348.27)] osgi.extender; (&(osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2.0.0)))]

 

What should I be doing to resolve this or what might I have added that requires this so I might see what happens if I remove a dependency that is causing this.

1 Accepted Solution

Avatar

Correct answer by
Level 4

I resolved this by removing dependencies and changing some servlet annotations so they did not use the 

@component

annotation from the osgi packages.

View solution in original post

21 Replies

Avatar

Correct answer by
Level 4

I resolved this by removing dependencies and changing some servlet annotations so they did not use the 

@component

annotation from the osgi packages.