How can I verify the CSSDK version?

I am building out a new development server in preparation for our upgrade to TS 6.7.1. The server is a Win2K3 EE server (no SP1 yet) and I did a fresh install of TS 6.7.1. We have several .Net applications that use the CSSDK web services to interact with TeamSite (originally developed against CSSDK 2.0) and they worked fine against TS 6.7.1.

As soon as I installed Service Pack 1 for TS 6.7.1 I started getting this error: System.Web.Services.Protocols.SoapException: An exception occurred: java.lang.NullPointerException. I'm guessing that the version of CSSDK on the server is not correct for TS 6.7.1 SP1, but I'm having trouble verifying the version of the CSSDK to confirm this.

Should I just go ahead and download and install CSSDK 3.1 and the associated SP1? Is the newest version of the CSSDK not installed with TS 6.7.1? Looking in the WSDL files on the server everything still references 2.0, but that may be necessary for backwards compatibility.

Find more posts tagged with

Comments

nbwoven

1. I think the approach you have in Mind should fix the issue .

2. You can verify the CSSDK versions from the CCPro UI .
Click on the About-->Details should give you the CSSDK Info ....
Interwoven ContentServices SOAP Client
Interwoven ContentServices SOAP Server

3. You need to make sure that the build number in the
["Interwoven\iw-home\cssdk\cssdkiface.jar"] is the same as the one in
["Interwoven\CSSDK_Client\cssdk\cssdksoap.jar"] .

Lex

Thanks for the reply. I did some more reading and I found that I shouldn't have to do anything with our applications to ensure compatibility with the new CSSDK since we are using SOAP (perhaps I'm not understanding something, though - this appears to be related to Java apps and not .Net apps?):

ContentServices for TeamSite 2.x applications accessing ContentServices over SOAP do not need to be recompiled, but do need to include all ContentServices for TeamSite 3.1 Service Pack 1 jar files (including the supplied third party jar files), found in cssdkclient-home\cssdk\*.jar, in their Java Classpaths, either instead of or before any references to ContentServices for TeamSite 2.x jar files.

I also checked the cssdk.log file (I should have done this initially) and found this error:

WARNING: com.systinet.wasp.services.com.interwoven.cssdk.sci.soap.filesys.FileServiceSOAPImpl - has thrown an application exception.
EXCEPTION: no message
java.lang.NullPointerException
at java.util.Date.getMillisOf(Date.java:938)
at java.util.Date.after(Date.java:911)
at com.interwoven.cssdk.sci.data.CSSessionCache.isExpired(CSSessionCache.java:652)
at com.interwoven.cssdk.sci.data.CSSessionCache.getSession(CSSessionCache.java:663)
at com.interwoven.cssdk.sci.filesys.FileServiceSciImpl.getDirectoryContents(FileServiceSciImpl.java:1393)
at com.interwoven.cssdk.sci.soap.filesys.FileServiceSOAPImpl.getDirectoryContents(FileServiceSOAPImpl.java:920)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.systinet.wasp.server.adaptor.JavaInvoker.invokeService(JavaInvoker.java:1598)
at com.systinet.wasp.server.adaptor.JavaInvoker.endInvoke(JavaInvoker.java:567)
at com.idoox.wasp.server.adaptor.JavaAdaptorImpl.endInvoke(JavaAdaptorImpl.java:76)
at com.idoox.wasp.server.AdaptorTemplate.javaInvocation(AdaptorTemplate.java:566)
at com.idoox.wasp.server.AdaptorTemplate.doDispatch(AdaptorTemplate.java:391)
at com.idoox.wasp.server.AdaptorTemplate.dispatch(AdaptorTemplate.java:324)
at com.idoox.wasp.server.ServiceConnector.dispatch(ServiceConnector.java:385)
at com.systinet.wasp.ServiceManagerImpl.dispatchRequest(ServiceManagerImpl.java:638)
at com.systinet.wasp.ServiceManagerImpl.dispatch(ServiceManagerImpl.java:475)
at com.systinet.wasp.ServiceManagerImpl$DispatcherConnHandler.handlePost(ServiceManagerImpl.java:2584)
at com.idoox.transport.http.server.Jetty$WaspHttpHandler.handle(Jetty.java:97)
at com.mortbay.HTTP.HandlerContext.handle(HandlerContext.java:1087)
at com.mortbay.HTTP.HttpServer.service(HttpServer.java:675)
at com.mortbay.HTTP.HttpConnection.service(HttpConnection.java:457)
at com.mortbay.HTTP.HttpConnection.handle(HttpConnection.java:317)
at com.mortbay.HTTP.SocketListener.handleConnection(SocketListener.java:99)
at com.mortbay.Util.ThreadedServer.handle(ThreadedServer.java:254)
at com.mortbay.Util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:607)
at java.lang.Thread.run(Thread.java:595)

Does this shed any light on what our issue might be? Thanks.