Return to Jive Software

Skip navigation
Up to Discussions in Support
485 Views 1 Reply Last post: Jan 9, 2009 7:14 AM by todd.west RSS
jzimmerlin Novice
jzimmerlin
42 posts since
Oct 3, 2005
Currently Being Moderated

Jan 8, 2009 12:23 PM

SOAP APIs removed in 2.5.x?

I've been working with Clearspace 2.0.x on an integration project for months now, sort of unfortunate timing with the 2.5 release coming shortly after we started coding on 2.0. We have a good deal of code in another system which uses the SOAP client API to manipulate objects in Clearspace.

 

We finally got around to trying out 2.5 and it is a big improvement in performance, functionality and overall finish. We were evaluating an upgrade to 2.5.x for the project and most of it looked pretty straightforward, until I checked the SOAP docs for 2.5 and saw this:

 

Note: In previous versions, Clearspace included a client API for access to SOAP-style web services. That API has been removed. To build a client, one approach is to use WSDL files provided by Clearspace.

 

So now we have to rewrite the object model code to use lower-level web service APIs? Why was this API suddenly removed?

todd.west Jive Employee
todd.west
15,926 posts since
Jul 14, 2008
Currently Being Moderated
Jan 9, 2009 7:14 AM in response to: jzimmerlin
Re: SOAP APIs removed in 2.5.x?

Hi,

 

Yes, you will need to generate your own code from the WSDL's in order to use the Webservices API. Luckily there are many tools out there which do this quickly and very easily. Much of your code won't change (object manipulation), just the code used for connecting/authenticating as well as getting services.

 

This client was removed for various reasons. It was becoming hard to maintain (needed to be updated with every release for multiple code types) and we felt it was something that would be best left up to the customer to generate in order to remain as flexible as possible. Thanks.

 

-Todd

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.