Binding issue with osgi.component not being resolved | Community
Skip to main content
R
RobertHarperFS
November 29, 2023
Solved

Binding issue with osgi.component not being resolved

  • November 29, 2023
  • 4 replies
  • 4577 views

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.

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 RobertHarperFS

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

@8220494

annotation from the osgi packages.

4 replies

Sudheer_Sundalam
Community Advisor
Sudheer_SundalamCommunity Advisor
Community Advisor
November 29, 2023

@robertharperfs ,

Which version of AEM are you on? Here is the supported versions information for the latest archetypes.

System Requirements

Archetype AEM as a Cloud Service AEM 6.5 Java SE Maven

46Continual6.5.7.0+8, 113.3.9+

 

    R
    RobertHarperFSAuthor
    November 29, 2023

    AEM 6.5.15

      DPrakashRaj
      Community Advisor
      DPrakashRajCommunity Advisor
      Community Advisor
      November 29, 2023

       A you check if aem core components are installed on your local aem? Is this maven build is your custom code or you just created a maven arch type project from 41 version and deployed it?

        R
        RobertHarperFSAuthor
        November 29, 2023

        This maven project is for building our customizations. It is a port from 6.2 and we haven't converted the classic UI components over to touch UI yet. That may happen next year. I'm trying to simplify the build/deploy process so that fewer mistakes are made when developers try to build and deploy the current archetype. 

        Updates and patches have been installed to my local instance. I'm just getting down to cleaning up the dependencies and resolving binding issues. All of the code builds and deploys as expected, I am now stuck on resolving this binding issue.

          Sudheer_Sundalam
          Community Advisor
          Sudheer_SundalamCommunity Advisor
          Community Advisor
          November 30, 2023

          I've noticed this line in the bundle manifest header when looking at the details in the OSGI bundle page.

          Require-Capability: osgi.extender; filter:="(&(osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2.0.0)))", osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))"

          This is not in my pom.xml file. Where would it be coming from and what would I do to fix this?


          @robertharperfs ,

          Try running the maven build using mvn -e -U -X clean install to run the build process in debug mode. That way you can find out which dependency is try to download that file.

            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            December 4, 2023

            @robertharperfs  Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

            Kautuk Sahni
            R
            RobertHarperFSAuthor
            December 4, 2023

            No I did not find any of the responses as all that helpful. Many were goose chases that wasted my time.

              R
              RobertHarperFSAuthorAccepted solution
              December 4, 2023

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

              @8220494

              annotation from the osgi packages.

                Terms & ConditionsAccessibility statement

                Loading footer...