Access sharepoint using webservices through web dynpro.

[Former Member]

Hi,

I have a requirement to access lists maintained in sharepoint through WebDynpro.

I tried using the standard webservices provided by sharepoint. A model was created for the webservice, But during the execution of the application the web service call failed with the following error:

Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. No deserializer found for XML type [http://schemas.microsoft.com/sharepoint/soap/][/definitions/types/s:schema/s:element[12]/s:complexType/s:sequence/s:element/s:complexType] to deserialize class [unknown]. Check if type mapping file is correct or right objects are passed.

Can somebody tell me how to resolve the deserialization error.

Thanks,

Ronnie

[Former Member · Accepted solution]

Ronnie,

Try to test your Sharepoint WS with WebServices Navigator application -- http://host:port/wsnavigator.

If it fails as well then you are out of luck -- not all possible XSD schemas are supported by WD WebService model... Try to access this WS with custom (external) library like Axis.

Valery Silaev

SaM Solutions

http://www.sam-solutions.net

[Former Member · Accepted solution]

Hi Valery,

I tried to use the specify the web service wsdl in the WebServices Navigator. While testing the same I got an error in the following format,

Cannot download WSDL from <u><https://<server>/_vti_bin/Lists.asmx?wsdl</u>: org.w3c.dom.Node.<init>()

Thanks

Ronnie

[Former Member · Accepted solution]

Ronnie,

I faced this issue before. WD fails to generate valid client proxies for some XML shemas. Error from wsnavigator means that there was generated Java code that tries to instantiate org.w3c.dom.Node (<init> is call to constructor), but it is impossible while Node is interface, not a class.

So this is bug in WS framework. We solve similar issue via wrapping original WS with custom WS developed on .NET and then using it from WD. So it was kind of proxy wrapping original service. The "proxy" service has quite simple in/out messages that could be used by SAP tools.

Valery Silaev

SaM Solutions

http://www.sam-solutions.net