This post is the fifth in a series of blog posts about customizing for Clearspace 2.x. The previous posts covered:
Several changes were made in Clearspace 2.0 that could impact your web services code, whether the code is for a client or new service. Generally, these changes were made to make the API easier to use, to add functionality (such as support for REST, new in version 2), or to remove a little-used feature that couldn't be made to work well.
ln version 2 Clearspace web services are built on the CXF framework. CXF evolved from XFire, the framework on which Clearspace version 1 web services were built. When upgrading, be sure to update your classpath to replace the XFire JAR file with the CXF JAR.
SOAP-based web services no longer support caching; references to caching have been removed from the web service client API.
If you're using the Clearspace web service client API (for SOAP web services), you'll need to update your references to some classes. To clarify the difference between the standard and web service client APIs, some class names were prefixed with "WS". The Upgrading Extensions to Version 2 documentation contains a list of the renamed classes; these are all in the com.jivesoftware.community.webservices package. Of course, this also means that signatures for some of the methods within the API itself have changed where these types were used.
Update some API references where arrays were used so that collections are used instead.
The .NET client API is no longer available. If you've got a .NET client, you'll need to rewrite it using another web service client library.
If you've written web services that expose Clearspace functionality, note that the WSUtil.getJiveContext method has been removed. Instead, as noted in the description of API changes, you should use Spring properties to obtain manager references.
Web services you've included in a plugin are no longer declared in the plugin.xml file. In version 2, when writing a web service for deployment in a plugin, you declare the web service in a spring.xml file included in your plugin. Use the conventions described in the Apache CXF user's guide.Here's an example
<bean id="echoServiceImpl" class="com.jivesoftware.clearspace.plugin.example.webservices.EchoServiceImpl /">
<bean id="saajInInterceptor" class="org.apache.cxf.binding.soap.saaj.SAAJInInterceptor" />
<bean id="wss4jInInterceptor" class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
<constructor-arg>
<map>
<entry key="passwordCallbackClass"
value="com.jivesoftware.community.webservices.server.xfire.PasswordHandler" />
<entry key="action" value="UsernameToken" />
</map>
</constructor-arg>
</bean>
<bean id="validationCheckInterceptor"
class="com.jivesoftware.community.webservices.server.xfire.ValidationCheckInterceptor">
<property name="jiveUserDetailsService" ref="jiveUserDetailsService" />
</bean>
<jaxws:endpoint id="echoService" address="/soap/EchoService">
<jaxws:implementor>
<ref bean="echoServiceImpl" />
</jaxws:implementor>
<jaxws:inInterceptors>
<ref bean="saajInInterceptor" />
<ref bean="wss4jInInterceptor" />
<ref bean="validationCheckInterceptor" />
</jaxws:inInterceptors>
</jaxws:endpoint>
In version 2 WSDL operation params have friendly names. You should get new version 2 WSDL.
In version 1 accessing web services via XML-RPC used two extra parameters for username and password; version 2 uses basic auth instead.
The information above along with more details can be found in the Upgrading Extensions to 2.0 documentation.
We also have a video (with an attached presentation) that shows more about using web services to access your data in Clearspace 2.0 with Andrew Wright, Jive Software Engineer.
