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

Polish datasource observation mechanism in content apps

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Neutral
    • 6.2
    • None
    • None
    • None
    • Kromeriz 156, UI Framework 7, UI Framework 8
    • 8

    Description

      primary goal

      • get away from the inevitable need of content changed events. In the new incarnation of the content app we try to stay away from the ContentChangedEvent since it is an error-prone and cumbersome way to communicate the changes. Instead we try to utilise the native datasource observation capabilities relief the app developer from having to send notifications manually.
      • browser views should not have any imperative logic re: refreshing the views. Instead e.g. the table should use Vaadin DataProvider API and data providers should optionally subscribe to the backend events

      possible solution

      • JCR - use the wrapper around observation mechanism
        • do not want to have too many listeners at once. Maybe create a singleton pool of the listeners, which would broadcast the changes to the data providers?
        • non-JCR: depends on the capabilities of the backend
          • there could be no capabilities (like REST)
          • we could provide e.g. smth like localised CCE: specific action injects the specific DS observation and pushes the event
            additional complications
        • we have some relying on the CCE in other places. E.g. details sub-apps catch them and automatically close once it is received.
        • how do we leverage that situation?

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                apchelintcev Aleksandr Pchelintcev
                apchelintcev Aleksandr Pchelintcev
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Time Spent - 2.9h Remaining Estimate - 1h
                      1h
                      Logged:
                      Time Spent - 2.9h Remaining Estimate - 1h
                      2.9h