Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-39027

resource change events are posted before the changed resource is committed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.9.x
    • Fix Version/s: 2.9.x
    • Component/s: Kernel
    • Labels:
      None
    • Previous Issue Keys:
      KNL-870

      Description

      this is related to KNL-809, KNL-808 and KNL-807 changes, where extra update events(content.upd.title, content.upd.access and content.upd.visibility) are posted, before the changed resource is actually committed.

      So when certain event watcher classes receive those update event, and constructed the underlying resources, those resources could still have the pre-update attribute values, which would be confusing. Plus if there is any runtime exception prevents the resource commits, the "resource changed" events would then be invalid.

      The suggested solution is to post those update event after resource is correctly committed/updated.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  k1team KERNEL TEAM (Inactive)
                  Reporter:
                  zqian Zhen Qian
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration