Sling API vs JCR API | Adobe Higher Education
Skip to main content
J
jeremylanssiers
Level 3
February 16, 2023

Sling API vs JCR API

  • February 16, 2023
  • 3 の返信
  • 5781 ビュー

AEM supports the use of both Sling APIs and JCR APIs. 

 

The docs mention "While the JCR is AEM’s content repository, its APIs are NOT the preferred method for interacting with the content. Instead prefer the AEM APIs (Page, Assets, Tag, and so on) or Sling Resource APIs as they provide better abstractions." 

 

Furthermore, "Broad use of JCR APIs’ Session and Node interfaces in an AEM application is code-smell. Ensure Sling APIs should be used instead."

 

Personally, I used the JCR API for creating nodes and properties in custom workflows.

And found it necessary to use the JCR API in the unit tests.

 

Did you personally come across any use cases where the JCR API is better than the sling API? 

And is it always a legitimate code smell? 

    このトピックへの返信は締め切られました。

    3 の返信

    A
    Adobe Employee
    aanchalsikkaAdobe Employee
    Adobe Employee
    February 16, 2023

    Hello @jeremylanssiers 

     

    You should be able to get some good pointers here https://www.slideshare.net/connectwebex/jcr-sling-or-aem-which-api-should-i-use-and-when

    https://stackoverflow.com/questions/45376376/jcr-api-or-apache-sling 

     

     

      arunpatidar
      Community Advisor
      arunpatidarCommunity Advisor
      Community Advisor
      February 16, 2023

      I can se only one use case when JCR api is better then Sling API

      It is when you write Event on nodetype, which sling does not supports.

       

      Always use Framework API first (AEM <-- Sling <--- JCR)

      Arun Patidar
        BrianKasingli
        Community Advisor and Adobe Champion
        BrianKasingliCommunity Advisor and Adobe Champion
        Community Advisor and Adobe Champion
        February 16, 2023

        I agree.

          Manu_Mathew_
          Community Advisor
          Manu_Mathew_Community Advisor
          Community Advisor
          February 17, 2023

          @jeremylanssiers The Sling API works at a higher, more abstract level than the JCR API. JCR is much faster than Sling

          https://experienceleague.adobe.com/docs/experience-manager-64/developing/bestpractices/jcr-integration.html?lang=en#:~:text=The%20Sling%20API%20works%20at,the%20ResourceProvider%20mechanism%20if%20needed.

           

            joerghoh
            Adobe Employee
            joerghohAdobe Employee
            Adobe Employee
            February 18, 2023

            Oh well, we are constantly trying to reduce the slack in Sling 🙂 and make its performance on par with JCR; of course it's always a bit of overhead, but Sling offers some nice features which JCR cannot do; mostly because it's a fixed API we cannot extend anymore.

              契約条件Accessibility statement

              Loading footer...