CSSDK - getFile() throws errors

Hi,

I am not able to understand this error... using CSSDK, I am connecting to the TeamSite SOAP server.
From there I try to get a file using the CSClient:

CSVPath waPath = new CSVPath("//myServer/iwstore4/main/myProject/WORKAREA/dir1/templatedata/file.txtl");
client.getFile(waPath);

This file and the vpath definitely exists: I copied the path from ContentCenter so it should be right.

Now I get this XML-Exception:
org.xml.sax.SAXException: Invalid element in com.interwoven.cssdk.client.axis.generated.CSFileData - creator
at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at org.apache.axis.client.Call.invoke(Call.java:2467)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.interwoven.cssdk.client.axis.generated.FileServiceBindingStub.getFileBasicData(FileServiceBindingStub.java:5199)
at com.interwoven.cssdk.client.axis.filesys.FileServiceAdapterImpl.getFileBasicData(FileServiceAdapterImpl.java:1734)
at com.interwoven.cssdk.common.impl.CSClientImpl.getFile(CSClientImpl.java:432)

Any explanation for that and how to resolve that?

Thanks!

Find more posts tagged with

Comments

cliff1

From the error, it looks like the client stubs or axis clients jars are out of sync with the server WSDL of SOAP version. Do you have a SOAP client based on the WSDL for the TeamSite server you are connecting to?

georgst

Hello cliff,

Thanks for your reply!

In fact, in com.interwoven.cssdk.client.axis.generated.CSFileData I do not find any "creator" attribute. In commonservice/Types.wsdl I *do* find it:

element name="creator" nillable="true" type="xsd:string"/

...
So, your thought seems to be right.
However, I do not quite understand why WSDL and stubs differ. I just copied all available libraries from iw-home/cssdk and iw-home/cssdk/java to my project. I am using Teamsite 6.7 with CSSDK 3.1.0.
Was there an update path where CSSDK and the systinet server might not have been updatet at the same time?

Where can I download the most recent java libraries and stubs from?

Thanks,

Kind regards
Georg

Jcse

Where can I download the most recent java libraries and stubs from?

Hi
Check www.findjar.com for recent java libraries.
HTH

balance_sdb.rptdesign

georgst

@Jcse This is definitely not the place where to find interwoven stub libraries...

@cliff, any hint?

cliff1

A couple of ideas/comments/suggestions:

1. It sounds like your basic premise is sound. However, AXIS has been known to change from release to release where stubs generated with version X.X are not compatible with version Y.Y. It would be best to generate your own stubs from the wsdl (/cssdk/wsdl folder) to match your axis client if you continue on this path. Axis documents how to do this: http://ws.apache.org/axis/java/user-guide.html#UsingWSDLWithAxis. I have not tried using the java wrapper with self generated stubs, so this is new territory for me. I've generally generated stubs for different languages (non java).

2. The "more typical" solution is to download the ContentServices SDK Client that corresponds to your TeamSite release. This should have everything you need to write a client application and stubs, java wrapper (cssdksoap.jar) and axis version should all be synchronized. Can grab the pieces you need and integrate them into your maven build.

3. If you are using TeamSite 6.7.2 SP1 (or later), you might want to look at the new CSJavaFactory instead of using SOAP. This factory allows remote access and is much faster than the SOAP interface. In fact, it is the factory being used for the ContentCenter webapp (the biggest CSSDK client app known to man). I don't know the constraints of your application, so use your judgment. If you need HTTPS or need to tunnel all access through iw-webd (port 80 or 443), probably better to stick with the SOAP interface. If your app is doing some heavy lifting and it's OK or it to have direct connection to iwserver, CSJavaFactory is probably better.

I hope some of this is useful. I have definitely written a generic CSSDK client app that can be switched between the SOAPFactory and LocalFactory (before JavaFactory existed) and it worked fine. When we switched ContentCenter from CSLocalFactory to CSJavaFactory, we honestly just changed the csssk.cfg file and classpath and everything worked (we found a couple of small CSJavaFactory bugs, but those were fixed).

-Cliff

georgst

cliff, that sounds perfect!

For the moment I am "forced" to use SOAP, as we probably will need to work remotely (and have TS 6.7.1). JNI is not an option currently... So SOAP will be the only way to go for now.

But so far, I am really glad to hear that you're successfully using CSClient!
For the future I'd like to establish an environment that's moving away from ugly Perl scripts.

Now, regarding your first approach, I've already tried exactly this solution. I was a bit struggeling with wrong namespaces / package names. In cssdksoap.jar there are some sub-packages with "pvt" suffix. And most important, the CSSOAPFactory is included in this jar. So it seems that stubs and other classes like the factory are intermingled within that jar... :-(

Tomorrow we're going to discuss aspects about the update to Teamsite 6.7.2 (SP1?) - - currently we have 6.7.1SP1 running. With CSJavaFactory it would be one more good argument to update.
Thanks for all these helpful ideas and suggestions.
I'll keep you uptodate!

Best
Georg

srinivasarao

We have added the "creator" element in the 6.7.1 SP1 release onwards.

Compatibility matrix.

CSSDK client
CS 3.0 -> TS 6.7.0
CS 3.1 --> TS 6.7.1
CS 3.1.0 SP1--> TS 6.7.1 SP1
CS 3.1.1 --> TS 6.7.2
CS 3..1.1 SP1 ---> TS 6.7.2 SP1

You have to use the corresponding CSSDK Client Jars based on the TS version, otherwise it will not work. Looks like you are using CS 3.1 client with TS 6.7.1 SP1 Server which is not compatible. upgrade your CS client to CS 3.1.0 SP1 in order to communicate with TS 6.7.1 SP1 server.

--Srinivas

georgst

Srinivas, thanks a lot for this important note.
Is there way of downloading CSSDK only instead of the whole Teamsite release (with > 800 MB)? I've access to interwoven/Autonomy's Download site but haven't found a suitable download package there.

Thanks for your help!
Georg

georgst

I've now downloaded and scanned Teamsite 6.7.1 SP1.
I was not able to find any cssdksoap.jar, thus no stub classes. What's the right place to look at?

srinivasarao

Content Services SDK can be downloaded separately.

URL :

https://support.interwoven.com/ESD2/UI_ESDSelProduct.asp?PCatID=69&CatName=ContentServices%20SDK

It is listed as a separate product under the Content Management Products.

regards
Srinivas

georgst

In my case, I only get a page with
"Welcome to the ESD System Downloads Center

Back -- Logoff -- Interwoven Support "...

So no product listing. No links to any downloads. I'll report this to the support.

Faizi

In my case, I only get a page with
"Welcome to the ESD System Downloads Center

Back -- Logoff -- Interwoven Support "...

So no product listing. No links to any downloads. I'll report this to the support.

Do you have support login?
If yes then you can find it otherwise not.

Adam Stoller

Do you have support login?
If yes then you can find it otherwise not.

You need both a support login and credentials that indicate you should have access to download the particular product piece you're looking for.

Without both you aren't likely to get too far.

Faizi

You need both a support login and credentials that indicate you should have access to download the particular product piece you're looking for.

Without both you aren't likely to get too far.

Yes! of course Adam. He should has credentials to download.

Thanks,

georgst

You need to be a "support contact". As of today, the links are visible and I can download the packages... but the way to get here felt like a ping-pong-game with the support team. :-/