Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-5529 Update mechanism improvements
  3. MAGNOLIA-2595

Update tasks : streamline class names, functionality and provide a couple more useful abstractions

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: updatemechanism
    • Labels:
      None

      Description

      • current naming is very inconsistent, makes it hard to find the appropriate task to use
      • the way some tasks work is inconsistent with others: some are very safe (check current values, etc), some aren't (just add a property no matter what the current status is) - we should add consistency and/or document the few inconsistency and why the safety is needed in most cases
      • we've often had the need for :
        • tasks which recurse through subnodes - an abstract task using a Visitor would be very helpful.
        • tasks which perform an operation over a given set of nodes - an abstract takes that operates on the nodes returned by a jcr query would help.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              gjoseph Magnolia International
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: