Alfresco Web Services on .Net Framework 2.0

[demondolphin]

Hi,

I want to write a .Net 2.0 smart client that uses the alfresco repository. I intend to use the Alfresco Web Services API to access the repository but I'm getting some difficulties to generate the classes from the provided wsdl files. Could anyone tell me what I have to do? I'm using the wsdl.exe tool to generate those classes.

Regards,

Eduardo

P.S: Sorry if this thread isn't in the right place.

[kbond]

I would be very interested to get your recipe because I would like to implement such thing with python. However I gont stuck with the authentication.

http://www.alfresco.org/forums/viewtopic.php?t=397
But unfortunatly nobody have answered…
Good luck

[rwetherall]

Hi Eduardo,

I haven't had chance to try our web services out from .NET, but I know other people have tried it with some success.

The only problem I have seen when generating code from our WSDL was in Ruby which fell over due to an anonymously declared complex type in header.xsd.

Try changing the WSDL in this file to:

<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.alfresco.org/ws/headers/1.0" xmlns:headers="http://www.alfresco.org/ws/headers/1.0" elementFormDefault="qualified" version="0.1">

   <complexType name="QueryConfiguration">
      <sequence>
         <element name="fetchSize" type="int" default="500"></element>
      </sequence>
   </complexType>

   <complexType name="LocaleConfiguration">
      <sequence>
         <element name="locale" type="string" maxOccurs="1" minOccurs="0"></element>
      </sequence>
   </complexType>
   
   <complexType name="NamespaceConfiguration">
      <sequence>
         <element name="mapping" maxOccurs="unbounded" minOccurs="0" type="NamespaceConfigurationInner"></element>
      </sequence>
   </complexType>
   
   <complexType name="NamespaceConfigurationInner">
     <sequence>
        <element name="prefix" type="NCName"></element>
        <element name="uri" type="string"></element>
     </sequence>
   </complexType>

</schema>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Hope this helps.
Roy