Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-54172

BandanaManager does not save value when listening for AbstractLikeEvent

    XMLWordPrintable

Details

    Description

      Summary

      we have developed a plugin where we listen for an AbstractLikeEvent. When it occurs, we want to use the BandanaManager to persist values in the database. This works before Confluence 6. Since Confluence 6, we can't save the information in the Bandana anymore. The (debug) log says, that it has saved the given information successfully in our own context, but when we are trying to get the keys for the specific context, it returns 0 items (although it said that the process was successful). After we have found the issue, we tried several Confluence versions. In Confluence 5 the BandanaManager works totally fine and as expected, but since Confluence 6 (until the latest version 6.5) the functionality seems to be broken. This problem only occurs when we are listening for AbstractLikeEvent's. When you try the same with e.g. a CommentCreateEvent, it works as expected (we set a value in our context and then fetch the keys from the BandanaManager). To make the issue more clear to you, we have prepared a minimal example plugin, where we are listening for the previously mentioned event and then try to save a value and get the Bandana keys. Please have a look in the example and try to reproduce the problem.

      Steps to Reproduce

      1. Handle the event AbstractLikeEvent
      2. Inside handleEvent, set the value using BandanaManager#setValue

      Expected Results

      BandanaManager writes value to database

      Actual Results

      BandanaManager does not write value to database

      Notes

      Replicated in version 6.5.0 but works as expected in version 5.10.7

      Attachments

        Issue Links

          Activity

            People

              fxu Feng Xu (Inactive)
              299e817c9ca5 Martin Gypser
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: