Confluence Docs 3.3 : Confluence SOAP Provider Migration
This page last changed on May 23, 2007 by rosie@atlassian.com.
Starting with the release of Confluence 1.4.3, and stretching through the next three major releases, Confluence will be transitioning from using the Glue library to provide a SOAP remote API, to using Apache Axis. Unfortunately, while the SOAP services will stay the same, the WSDL that these libraries generate to interact with the same services will change, so SOAP applications that interact with Confluence will need to migrate with us. The migration should be relatively painless. Since the underlying objects represented by the WSDL are still the same, the process should involve regenerating your SOAP stubs, and a few cosmetic code changes. The XML-RPC API is unaffected by this change. Current Status
Progress on these issues can also be tracked via CONF-3141 The PlanAs of version 1.4.3, Confluence ships with three SOAP endpoints:
Over the next three major Confluence releases we will:
What This Means for SOAP ClientsConfluence major releases occur every three or four months. Thus, authors of SOAP clients should keep in mind this timeline, starting with the release of Confluence 2.0 (November 2005)
|
![]() |
Document generated by Confluence on Jul 09, 2010 01:10 |