[Fedora-suds-list] suds and Exchange Web Services

[Jon Wynacht]

Thanks for all the input on this; been on vacation and just now getting back to these emails.

I'm going to try the beta/release .4 and see how that works out. There's also an in-house C# developer that has some ideas about using an intermediary service I can connect to. We shall see...

Cheers,

Jon

On Sep 2, 2010, at 3:11 PM, jon at objectevolution.com wrote:

> Hi,
> 
> I'm using the suds-ews branch to "try" and connect to Exchange Web Services for a client. Couple things I've run into:
> 
> 1. I need to bring Services.wsdl, messages.xsd and types.xsd local and not on the Exchange server so I could modify Services.wsdl and append the following:
> 
> <wsdl:service name="ExchangeServices">
>        <wsdl:port name="ExchangeServicePort" binding="tns:ExchangeServiceBinding">
>                <soap:address location="https://exchange.server.com/ews/Exchange.asmx" />
>        </wsdl:port>
>    </wsdl:service>
> 
> 2. Now, I get the client creation in Python just fine but when I go to call a service it wants me to, obviously, authenticate.
> 
> I can authenticate to the server upon client creation but I get a bad wsdl which needs the xml snippet from above. I can go local with the wsdl but then I need to authenticate to call a service.
> 
> Can the client call a service and pass a transport as well?
> 
> Thanks,
> 
> Jon
> 
> _______________________________________________
> suds mailing list
> suds at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/suds