Why certain folders are grayed out in AEM 6.4 under /libs | Community
Skip to main content
E
Eakambaram
Level 3
September 6, 2018
Solved

Why certain folders are grayed out in AEM 6.4 under /libs

  • September 6, 2018
  • 2 replies
  • 3997 views

In AEM 6.4 we are noticing certain folders under /libs are grayed out. We have not seen thing AEM 6.1.

Are they deprecated or are we not supposed to extend/use/refer them?

Any one please let us know the exact reason Why certain folders are grayed out in AEM 6.4 under /libs

    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 edubey

    Here is the details for all new node properties to these similar node

    In order to make it safer and easier for customers to understand what areas of /libs are safe to use and overlay the content in /libs has been classified with the following mixins:

    • Public (granite:PublicArea) - Defines a node as public so that it can overlaid, inherited (sling:resourceSuperType) or used directly (sling:resourceType). Nodes beneath /libs marked as Public will be safe to upgrade with the addition of a Compatibility Package. In general customers should only leverage nodes marked as Public.
    • Abstract (granite:AbstractArea) - Defines a node as abstract. Nodes can be overlaid or inherited (sling:resourceSupertype) but must not be used directly (sling:resourceType).
    • Final (granite:FinalArea) - Defines a node as final. Nodes classified as final cannot be overlaid or inherited. Final nodes can be used directly via sling:resourceType. Subnodes under final node are considered internal by default
    • Internal (granite:InternalArea) - Defines a node as internal. Nodes classified as internal cannot be overlaid, inherited, or used directly. These nodes are meant only for internal functionality of AEM
    • No Annotation - Nodes inherit classification based on the tree hierachy. The / root is by default Public. Nodes with a parent classified as Internal or Final are also to be treated as Internal.

    2 replies

    V
    Adobe Employee
    vish.dhaliwalAdobe Employee
    Adobe Employee
    September 6, 2018

    Hello,

    Please check section "Content Classifications" in the doc [1] to know the meaning of each mixintype

    [1] Adobe Experience Manager Help | Sustainable Upgrades

    Regards,

    Vishu

    edubey
    edubeyAccepted solution
    Level 10
    September 7, 2018

    Here is the details for all new node properties to these similar node

    In order to make it safer and easier for customers to understand what areas of /libs are safe to use and overlay the content in /libs has been classified with the following mixins:

    • Public (granite:PublicArea) - Defines a node as public so that it can overlaid, inherited (sling:resourceSuperType) or used directly (sling:resourceType). Nodes beneath /libs marked as Public will be safe to upgrade with the addition of a Compatibility Package. In general customers should only leverage nodes marked as Public.
    • Abstract (granite:AbstractArea) - Defines a node as abstract. Nodes can be overlaid or inherited (sling:resourceSupertype) but must not be used directly (sling:resourceType).
    • Final (granite:FinalArea) - Defines a node as final. Nodes classified as final cannot be overlaid or inherited. Final nodes can be used directly via sling:resourceType. Subnodes under final node are considered internal by default
    • Internal (granite:InternalArea) - Defines a node as internal. Nodes classified as internal cannot be overlaid, inherited, or used directly. These nodes are meant only for internal functionality of AEM
    • No Annotation - Nodes inherit classification based on the tree hierachy. The / root is by default Public. Nodes with a parent classified as Internal or Final are also to be treated as Internal.
      Terms & ConditionsAccessibility statement

      Loading footer...