Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4999

Revisit UI context components clean-up/destruction mechanisms

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Neutral
    • 6.2
    • None
    • None
    • None
    • UI Framework 2, UI Framework 6
    • 8

    Description

      We've introduced view destruction functionality, which allows to unregister it and clean-up the bean storages of it and its child views.

      However, the accompanying objects, like presenters, observers etc might also need destruction which at this point is done via type checking (i.e. instanceof Destructible and manual call of destroy method.

      Problem is that most of such manually cleaned-up objects are actually created by the view and could be managed/tracked along-side of the view and could be destroyed along with it.

      goals:

      • retrospect on the Destructible interface usage, is there too much of boilerplate caused by it, is it convenient?
      • consider ways of tracking/automating the clean-up and destruction of view-bound instances.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              rkovarik Roman Kovařík
              apchelintcev Aleksandr Pchelintcev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoR

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0d
                    0d
                    Logged:
                    Time Spent - 7h 25m
                    7h 25m