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

Studio plugins: Using components not available to plugins

    XMLWordPrintable

Details

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Hi

      In studio we use few Confluence's components that are not exposed as available to plugins.
      Can you please have a look at our code and either make those components public (available to plugins) or suggest a better way to achieve desired functionality.

      Currently we use ComponentLocator that goes directly to SpringContainer to get these components.
      List of places where we use ComponentLocator:

      Where Why
      ConfluenceTrustedApplicationsSynchroniser Adding trusted application entry
      ConfluenceLicenseHandler Setting a licence
      ConfluencePluginScheduler Scheduling jobs
      ConfluenceCertificateFactory Making trusted calls
      CrowdNotifyServlet Recalculating active user count when user is added/removed in crowd
      ConfluenceQuickNavProvider Doing QuickNav search in Studio

      Thanks

      Attachments

        Activity

          People

            cmiller CharlesA
            dhornik DusanA
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: