suds and Exchange Web Services

[Jon Wynacht]

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

[Joshua J. Kugler]

On Thursday 02 September 2010, jon(a)objectevolution.com elucidated thus:
>  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? 
Take a look at: 
http://lists.fedoraproject.org/pipermail/suds/2010-July/001046.html

The other "exchange" threads on this page make for good reading too:

http://lists.fedoraproject.org/pipermail/suds/2010-July/thread.html

j

-- 
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com - Fairbanks, AK
PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A

[Glen Walker]

Another option, if you're using suds 0.4.0 beta, is to use a plugin to manipulate the
WSDL as it is loaded by suds. See
https://fedorahosted.org/suds/wiki/Documentation#Version2 for details of the plugin API.

A plugin something like this might do the trick:


import xml.ns

import suds.plugin
import suds.sax.element
import suds.sax.attribute

class ServiceAddPlugin(suds.plugin.DocumentPlugin):

    def parsed(self, context):

        # context.document is the root element of the WSDL document.
        definitions_element = context.document

        # Make sure we are dealing with a WSDL document.
        if definitions_element.namespace()[1] != xml.ns.WSDL.BASE or \
          definitions_element.name != 'definitions':
            return

        # Find the namespace prefix used for WSDL elements.
        wsdl_prefix = definitions_element.findPrefix(xml.ns.WSDL.BASE,
                                                     default='wsdl')
        wsdl_namespace = (wsdl_prefix, xml.ns.WSDL.BASE)

        # Find the namespace prefix used for SOAP elements.
        soap_prefix = definitions_element.findPrefix(xml.ns.WSDL.BIND_SOAP,
                                                     default='soap')
        soap_namespace = (soap_prefix, xml.ns.WSDL.BIND_SOAP)

        # Find the WSDL target namespace URI and prefix (if any).
        target_namespace = definitions_element.get('targetNamespace')
        target_namespace_prefix = \
          definitions_element.findPrefix(target_namespace)

        # Create a wsdl:service element and add to the wsdl:definitions.
        service_element = suds.sax.element.Element('service', ns=wsdl_namespace)
        definitions_element.append(service_element)

        # Add a name attribute to the wsdl:service element.
        name_attribute = \
          suds.sax.attribute.Attribute('name', 'ExchangeServices')
        service_element.append(name_attribute)

        # Create a wsdl:port element and add to the wsdl:service.
        port_element = suds.sax.element.Element('port', ns=wsdl_namespace)
        service_element.append(port_element)

        # Add a name attribute to the wsdl:port element.
        name_attribute = suds.sax.attribute.Attribute('name',
                                                      'ExchangeServicePort')
        port_element.append(name_attribute)

        # Create a prefix for the target namespace if it wasn't already defined.
        if target_namespace_prefix is None:
            target_namespace_prefix = 'tns'
            port_element.addPrefix(target_namespace_prefix, target_namespace)

        # Add a binding attribute to the wsdl:port element.
        binding = '%s:%s' % (target_namespace_prefix,
'ExchangeServiceBinding')
        name_attribute = suds.sax.attribute.Attribute('binding', binding)
        port_element.append(name_attribute)

        # Create a soap:address element and add to the wsdl:port.
        address_element = suds.sax.element.Element('address',
                                                   ns=soap_namespace)
        port_element.append(address_element)

        # Add a location attribute to the soap:address element.
        location_attribute = suds.sax.attribute.Attribute('location',
          'https://exchange.server.com/ews/Exchange.asmx')
        address_element.append(location_attribute)



-----Original Message-----
From: suds-bounces(a)lists.fedoraproject.org [mailto:[e-mail]]
On Behalf Of jon(a)objectevolution.com
Sent: Friday, 3 September 2010 10:12 a.m.
To: suds(a)lists.fedoraproject.org
Subject: [Fedora-suds-list] suds and Exchange Web Services

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
This email and attachments: are confidential; may be protected by privilege and copyright;
if received in error may not be used, copied, or kept; are not guaranteed to be
virus-free; may not express the views of Kordia(R); do not designate an information
system; and do not give rise to any liability for Kordia(R).

[Erik Cederstrand]

Hi Jon

I'm working on a python module for Exchange. There are various other problems using
Exchange together with Suds, one being that Exchange (despite the XSD) needs some calls to
be in a specific XML format that Suds is unable to generate. Another problem is that Suds
doesn't offer connection  pooling, which is important to me, as I'm doing
high-volume content creation in Exchange.

If you, or anyone else, is interested in helping out please send me a note.

Thanks,
Erik

Den 03/09/2010 kl. 00.11 skrev jon(a)objectevolution.com:

>  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(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds

[Joshua J. Kugler]

On Thursday 02 September 2010, Erik Cederstrand elucidated thus:
>  Hi Jon
>
>  I'm working on a python module for Exchange. There are various other
>  problems using Exchange together with Suds, one being that Exchange
>  (despite the XSD) needs some calls to be in a specific XML format
>  that Suds is unable to generate. Another problem is that Suds doesn't
>  offer connection  pooling, which is important to me, as I'm doing
>  high-volume content creation in Exchange.
>
>  If you, or anyone else, is interested in helping out please send me a
>  note. 
I am by no means a SOAP expert, certainly not MS's perversion of it, but 
I do have access to an account on an Exchange server, so would at least 
be able to test the mail sending/receiving portion of it.

j

-- 
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com - Fairbanks, AK
PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A

[Glen Walker]

Hi Erik,

>  There are various other problems using Exchange together with Suds,
> one being that Exchange (despite the XSD) needs some calls to be in a specific XML format
> that Suds is unable to generate. 
I have recently been dealing with the SOAP API of a
vendor that might have similar issues. Key problems with it are:
 1) Provides WSDL that doesn't quite match their implementation
 2) Replies with faults that aren't inside a Fault element
 3) Provides some XSD that is not well-formed XML
 4) Considers certain empty and attributeless elements to have a different meaning to
absense of the element.
    Suds however considers an empty and attributeless element to be superfluous and
won't include it in SOAP calls.

I have worked around these problems using suds 0.0.4 beta and a combination of custom
suds.plugin.DocumentPlugin and suds.plugin.MessagePlugin objects. The workaround that
might be relevant to your issue with Exchange (#4 above) was solved by using a
suds.plugin.DocumentPlugin to dynamically add a dummy attribute to the problem elements in
the XSD, and a suds.plugin.MessagePlugin to dynamically remove the dummy attribute from
the SOAP envelope before it is sent.

I could give you a hand with this aspect if it is of any use to you.

Kind Regards,
Glen


-----Original Message-----
From: suds-bounces(a)lists.fedoraproject.org [mailto:[e-mail]]
On Behalf Of Erik Cederstrand
Sent: Friday, 3 September 2010 7:53 p.m.
To: jon(a)objectevolution.com
Cc: suds(a)lists.fedoraproject.org
Subject: Re: [Fedora-suds-list] suds and Exchange Web Services

Hi Jon

I'm working on a python module for Exchange. There are various other problems using
Exchange together with Suds, one being that Exchange (despite the XSD) needs some calls to
be in a specific XML format that Suds is unable to generate. Another problem is that Suds
doesn't offer connection  pooling, which is important to me, as I'm doing
high-volume content creation in Exchange.

If you, or anyone else, is interested in helping out please send me a note.

Thanks,
Erik

Den 03/09/2010 kl. 00.11 skrev jon(a)objectevolution.com:

>  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(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds 
This email and attachments: are confidential; may be protected by privilege and copyright;
if received in error may not be used, copied, or kept; are not guaranteed to be
virus-free; may not express the views of Kordia(R); do not designate an information
system; and do not give rise to any liability for Kordia(R).

[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(a)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(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds