Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-3141

Migrate SOAP API to Axis

XMLWordPrintable

    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      The problem is that we're probably going to break every existing SOAP tool in the process: especially TimTam and the command-line client, both of which are quite popular amongst users.

      The migration should ideally be done over the course of a couple of versions: perhaps in 1.5 supply parallel SOAP services using both libraries, then phase out Glue in 1.6 or 1.7

      See http://confluence.atlassian.com/display/DOC/Confluence+SOAP+Provider+Migration

          1.
          		 Make default SOAP service configurable Sub-task Closed Unassigned
          2.
          		 Remove Glue SOAP service Sub-task Closed Unassigned

              Unassigned Unassigned
              cmiller@atlassian.com Charles Miller (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: