Uploaded image for project: 'Magnolia Resources Module'
  1. Magnolia Resources Module
  2. MGNLRES-229

Rethink actions in resource app

    XMLWordPrintable

Details

    • Story
    • Resolution: Won't Do
    • Neutral
    • None
    • None
    • None
    • None

    Description

      The resources app (since 2.4) uses its own flavors of Container/Items, based on the new resources APIs from Magnolia 5.4.
      Some of those resources still live in the resources JCR workspace, so we typically have to support the same use cases as for JCR-based content apps (e.g. publish/version actions, status column), yet only for selected resources.

      We currently customize almost every action and workbench component for this purpose, just to do one same thing:

      • Ask the LayeredOrigin if current resource is coming from JCR
      • If so, "unwrap" the underlying JCR resource; we typically only get a path
      • Get the Node from its path via Context or indirectly through Node|SessionUtils
      • Wrap it as a JcrNodeAdapter so that the super impl can work with it.

      It feels quite sub-optimal; we're looking for a more elegant approach to arouse reuse of the content-app framework altogether, for JCR resources (thus removing need for most action & component customizations).

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              mgeljic Mikaël Geljić
              mgeljic Mikaël Geljić
              Nucleus
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD