"no services defined" with Microsoft Exchange Web Services

[Mathieu Dupuy]

Hi suds people.
I have to use suds for talking to a Microsoft Exchange Web Service in
order to do stuff like creating meetings. book rooms and stuffs. I do
it in python, and choosed suds for dealing with the SOAP.
So far I was using a patched version of suds 0.3.7, patched for
dealing better with EWS SOAP (suds-ews :
https://bitbucket.org/daevaorn/suds-ews/). But I don't want to use
that outdated version anymore.

I grabbed the last version of suds from pip, the one from jurko which
contains most of the patchs proposed since the development have
stalled, and I have got the following error (I have it too even with
the "regular" suds 0.4.0 release):

----------------
Traceback (most recent call last):
  File "sudstest.py", line 15, in <module>
    client.service.CreateItem(None, calitem)
  File "/usr/local/lib/python2.7/dist-packages/suds/client.py", line
293, in __getattr__
    port = self.__find(0)
  File "/usr/local/lib/python2.7/dist-packages/suds/client.py", line
328, in __find
    raise Exception, 'No services defined'
Exception: No services defined
----------------

The code that produce the error is a simple client snippet, which was
almost the same that was working fine with 0.3.7.
----------------
from suds.transport.https import WindowsHttpAuthenticated
from suds.client import Client
from suds.sax.element import Element

ntlm = WindowsHttpAuthenticated(username='xxx', password='xxx')
client = Client('https://exca010.encara.local.ads/ews/Services.wsdl',
transport=ntlm)
ns = ('t', 'http://schemas.microsoft.com/exchange/services/2006/types')
soap_headers = Element('RequestServerVersion', ns=ns)
soap_headers.attributes.append('Version="Exchange2010_SP1"')
client.set_options(soapheaders=soap_headers)

calitem = client.factory.create('t:CalendarItem')
client.service.CreateItem(None, calitem)
----------------

I'm really can't figure out what causes the problem. It should work
fine out of the box.
I hope you people of the suds ML can bring some help.
Thank you very much.

[Jurko Gospodnetić]

   Hi.

>  So far I was using a patched version of suds 0.3.7, patched for
>  dealing better with EWS SOAP (suds-ews :
>  https://bitbucket.org/daevaorn/suds-ews/). But I don't want to use
>  that outdated version anymore. 
>  I grabbed the last version of suds from pip, the one from jurko
> which
>  contains most of the patchs proposed since the development have
>  stalled, and I have got the following error (I have it too even with
>  the "regular" suds 0.4.0 release): 
   In general I suggest using suds-jurko from the sources at the moment. 
There have been many fixes & cleanups since the last formal release. For 
that matter, I would like to package the current state as the next 
formal release, just waiting for some people using it to sent me back a 
confirmation that everything is working fine for them.

   In that versions we've added automated tests checking parts of suds 
without having to connect to an external web service, e.g. by using 
hardcoded WSDL schemes, injecting fake server responses etc. That code 
can now easily be used to reproduce any problematic behaviour without 
having to use an externally provided web service. And once you have such 
a working locally reproducible test case, you can even change the 
naming, remove unnecessary details and such - making both the problem 
easier to debug and removing any proprietary information that might have 
otherwise prevented you from sending out the code needed to reproduce 
the problem.


>  I'm really can't figure out what causes the problem. It
> should work
>  fine out of the box.
>  I hope you people of the suds ML can bring some help. 
   We have not done anything related to EWS there (nor have we ever used 
it) so its doubtful your problem has been fixed out-of-the-box.

   And as for that, if you can let me know how to connect to that web 
service, or at least get me the WSDL in question I can take a look at 
what's breaking and what workarounds for any of the problems involved 
have been made in the patched SOAP version you mentioned. I have not 
tried out your code, assuming I'd need some sort of a username & 
password to make it work.


   Best regards,
     Jurko Gospodnetić

[Gauthier Bastien]

Hi,

we use suds 0.4 in several projects and we could update our package to 
use your fork.

But what I would like to know is, what is the real current state of the 
project?  I understand that forking to bitbucket/github and so on is 
easy, but is there a plan to make it useable by everybody and what is 
the current official repository?

The current svn seems dead, is it possible to specify on the suds home 
page that the code to use is on another repos?  We could even configure 
TRAC to display another official repository on bitbucket or any other 
source repo...

I think it would be great because looking at the current state, and last 
changes (nothing done for years) make people believe the project is 
dead, and maybe it is not the case...

Thank you and have a nice day,

Gauthier Bastien
<http://www.imio.be>
Zoning industriel, 34
5190 Mornimont
Tél: [phone]
Fax: [phone]
gauthier.bastien(a)imio.be <mailto:[e-mail]>
	
La mutualisation informatique
au service des pouvoirs locaux

Le 12/06/13 14:29, Jurko Gospodnetić a écrit :
>    Hi.
>
> > So far I was using a patched version of suds 0.3.7, patched for
> > dealing better with EWS SOAP (suds-ews :
> > https://bitbucket.org/daevaorn/suds-ews/). But I don't want to use
> > that outdated version anymore.
>
> > I grabbed the last version of suds from pip, the one from jurko which
> > contains most of the patchs proposed since the development have
> > stalled, and I have got the following error (I have it too even with
> > the "regular" suds 0.4.0 release):
>
>    In general I suggest using suds-jurko from the sources at the 
>  moment. There have been many fixes & cleanups since the last formal 
>  release. For that matter, I would like to package the current state as 
>  the next formal release, just waiting for some people using it to sent 
>  me back a confirmation that everything is working fine for them.
>
>    In that versions we've added automated tests checking parts of suds 
>  without having to connect to an external web service, e.g. by using 
>  hardcoded WSDL schemes, injecting fake server responses etc. That code 
>  can now easily be used to reproduce any problematic behaviour without 
>  having to use an externally provided web service. And once you have 
>  such a working locally reproducible test case, you can even change the 
>  naming, remove unnecessary details and such - making both the problem 
>  easier to debug and removing any proprietary information that might 
>  have otherwise prevented you from sending out the code needed to 
>  reproduce the problem.
>
>
> > I'm really can't figure out what causes the problem. It should work
> > fine out of the box.
> > I hope you people of the suds ML can bring some help.
>
>    We have not done anything related to EWS there (nor have we ever 
>  used it) so its doubtful your problem has been fixed out-of-the-box.
>
>    And as for that, if you can let me know how to connect to that web 
>  service, or at least get me the WSDL in question I can take a look at 
>  what's breaking and what workarounds for any of the problems involved 
>  have been made in the patched SOAP version you mentioned. I have not 
>  tried out your code, assuming I'd need some sort of a username & 
>  password to make it work.
>
>
>    Best regards,
>      Jurko Gospodnetić
>
>  _______________________________________________
>  suds mailing list
>  suds(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds

[Matthew Ashton]

Mathieu, what is the __str__() of the client object you've created? You
should be able to see a list of services, ports, methods, and types

and Gauthier, I think that question deserves its own thread

On Wed, Jun 12, 2013 at 9:17 AM, Gauthier Bastien <gauthier(a)imio.be&gt; wrote:

>   Hi,
>
>  we use suds 0.4 in several projects and we could update our package to use
>  your fork.
>
>  But what I would like to know is, what is the real current state of the
>  project?  I understand that forking to bitbucket/github and so on is easy,
>  but is there a plan to make it useable by everybody and what is the current
>  official repository?
>
>  The current svn seems dead, is it possible to specify on the suds home
>  page that the code to use is on another repos?  We could even configure
>  TRAC to display another official repository on bitbucket or any other
>  source repo...
>
>  I think it would be great because looking at the current state, and last
>  changes (nothing done for years) make people believe the project is dead,
>  and maybe it is not the case...
>
>  Thank you and have a nice day,
>
>     Gauthier Bastien   <http://www.imio.be>
>  Zoning industriel, 34
>  5190 Mornimont
>  Tél: [phone]
>  Fax: [phone]
>  gauthier.bastien(a)imio.be
>
>  La mutualisation informatique
>  au service des pouvoirs locaux
>  Le 12/06/13 14:29, Jurko Gospodnetić a écrit :
>
>    Hi.
>
>  So far I was using a patched version of suds 0.3.7, patched for
>  dealing better with EWS SOAP (suds-ews :
>  https://bitbucket.org/daevaorn/suds-ews/). But I don't want to use
>  that outdated version anymore.
>
>
>  I grabbed the last version of suds from pip, the one from jurko which
>  contains most of the patchs proposed since the development have
>  stalled, and I have got the following error (I have it too even with
>  the "regular" suds 0.4.0 release):
>
>
>    In general I suggest using suds-jurko from the sources at the moment.
>  There have been many fixes & cleanups since the last formal release. For
>  that matter, I would like to package the current state as the next formal
>  release, just waiting for some people using it to sent me back a
>  confirmation that everything is working fine for them.
>
>    In that versions we've added automated tests checking parts of suds
>  without having to connect to an external web service, e.g. by using
>  hardcoded WSDL schemes, injecting fake server responses etc. That code can
>  now easily be used to reproduce any problematic behaviour without having to
>  use an externally provided web service. And once you have such a working
>  locally reproducible test case, you can even change the naming, remove
>  unnecessary details and such - making both the problem easier to debug and
>  removing any proprietary information that might have otherwise prevented
>  you from sending out the code needed to reproduce the problem.
>
>
>  I'm really can't figure out what causes the problem. It should work
>  fine out of the box.
>  I hope you people of the suds ML can bring some help.
>
>
>    We have not done anything related to EWS there (nor have we ever used
>  it) so its doubtful your problem has been fixed out-of-the-box.
>
>    And as for that, if you can let me know how to connect to that web
>  service, or at least get me the WSDL in question I can take a look at
>  what's breaking and what workarounds for any of the problems involved have
>  been made in the patched SOAP version you mentioned. I have not tried out
>  your code, assuming I'd need some sort of a username & password to make it
>  work.
>
>
>    Best regards,
>      Jurko Gospodnetić
>
>  _______________________________________________
>  suds mailing list
>  suds(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds
>
>
>
>  _______________________________________________
>  suds mailing list
>  suds(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds
>

[Mathieu Dupuy]

This is all I got :
--------
> >> print str(client) 
Suds ( https://fedorahosted.org/suds/
)  version: 0.4.1 jurko 5
(development)

--------

Whereas with version I use, I've got a very long list of services :
--------
Suds ( https://fedorahosted.org/suds/ )  version: 0.3.7 GA  build:
R580-20091016

Service ( ExchangeServices ) tns="
http://schemas.microsoft.com/exchange/services/2006/messages"
   Prefixes (2)
      ns0 = "http://schemas.microsoft.com/exchange/services/2006/messages"
      ns1 = "http://schemas.microsoft.com/exchange/services/2006/types"
   Ports (1):
      (ExchangeServicePort)
         Methods (60):
            AddDelegate(ns1:EmailAddressType Mailbox,
ns1:ArrayOfDelegateUserType DelegateUsers, ns1:DeliverMeetingRequestsType
DeliverMeetingRequests, )(ns1:NonEmptyArrayOfApplyConversationActionType
ConversationActions, )
[...]
--------

It seems that indeed there has been a silent error in the consumming of the
WSDL.


On Wed, Jun 12, 2013 at 6:04 PM, Matthew Ashton
<matthew.ashton3(a)gmail.com&gt;wrote:

>  Mathieu, what is the __str__() of the client object you've
> created? You
>  should be able to see a list of services, ports, methods, and types
>
>  and Gauthier, I think that question deserves its own thread
>
>
>  On Wed, Jun 12, 2013 at 9:17 AM, Gauthier Bastien <gauthier(a)imio.be&gt;wrote:
>
> >  Hi,
> >
> > we use suds 0.4 in several projects and we could update our package to
> > use your fork.
> >
> > But what I would like to know is, what is the real current state of the
> > project?  I understand that forking to bitbucket/github and so on is easy,
> > but is there a plan to make it useable by everybody and what is the current
> > official repository?
> >
> > The current svn seems dead, is it possible to specify on the suds home
> > page that the code to use is on another repos?  We could even configure
> > TRAC to display another official repository on bitbucket or any other
> > source repo...
> >
> > I think it would be great because looking at the current state, and last
> > changes (nothing done for years) make people believe the project is dead,
> > and maybe it is not the case...
> >
> > Thank you and have a nice day,
> >
> >    Gauthier Bastien   <http://www.imio.be>
> > Zoning industriel, 34
> > 5190 Mornimont
> > Tél: [phone]
> > Fax: [phone]
> > gauthier.bastien(a)imio.be
> >
> > La mutualisation informatique
> > au service des pouvoirs locaux
> > Le 12/06/13 14:29, Jurko Gospodnetić a écrit :
> >
> >   Hi.
> >
> > So far I was using a patched version of suds 0.3.7, patched for
> > dealing better with EWS SOAP (suds-ews :
> > https://bitbucket.org/daevaorn/suds-ews/). But I don't want to use
> > that outdated version anymore.
> >
> >
> > I grabbed the last version of suds from pip, the one from jurko which
> > contains most of the patchs proposed since the development have
> > stalled, and I have got the following error (I have it too even with
> > the "regular" suds 0.4.0 release):
> >
> >
> >   In general I suggest using suds-jurko from the sources at the moment.
> > There have been many fixes & cleanups since the last formal release. For
> > that matter, I would like to package the current state as the next formal
> > release, just waiting for some people using it to sent me back a
> > confirmation that everything is working fine for them.
> >
> >   In that versions we've added automated tests checking parts of suds
> > without having to connect to an external web service, e.g. by using
> > hardcoded WSDL schemes, injecting fake server responses etc. That code can
> > now easily be used to reproduce any problematic behaviour without having to
> > use an externally provided web service. And once you have such a working
> > locally reproducible test case, you can even change the naming, remove
> > unnecessary details and such - making both the problem easier to debug and
> > removing any proprietary information that might have otherwise prevented
> > you from sending out the code needed to reproduce the problem.
> >
> >
> > I'm really can't figure out what causes the problem. It should work
> > fine out of the box.
> > I hope you people of the suds ML can bring some help.
> >
> >
> >   We have not done anything related to EWS there (nor have we ever used
> > it) so its doubtful your problem has been fixed out-of-the-box.
> >
> >   And as for that, if you can let me know how to connect to that web
> > service, or at least get me the WSDL in question I can take a look at
> > what's breaking and what workarounds for any of the problems involved have
> > been made in the patched SOAP version you mentioned. I have not tried out
> > your code, assuming I'd need some sort of a username & password to make it
> > work.
> >
> >
> >   Best regards,
> >     Jurko Gospodnetić
> >
> > _______________________________________________
> > suds mailing list
> > suds(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/suds
> >
> >
> >
> > _______________________________________________
> > suds mailing list
> > suds(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/suds
> >
>
>
>  _______________________________________________
>  suds mailing list
>  suds(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds
>

[Matthew Ashton]

My best guess would be to diff the two version's files to see the
discrepancies between them when consuming the WSDL..

it's odd that one would fail and the other would read the file :\

but have you tried with the newest version of suds? perhaps set up a
virtualenv , source bin/activate , install suds 4.0 and see what you get?

On Thu, Jun 13, 2013 at 4:06 AM, Mathieu Dupuy <deronnax(a)gmail.com&gt; wrote:

>  This is all I got :
>  --------
>  >>> print str(client)
>  Suds ( https://fedorahosted.org/suds/ )  version: 0.4.1 jurko 5
>  (development)
>
>  --------
>
>  Whereas with version I use, I've got a very long list of services :
>  --------
>  Suds ( https://fedorahosted.org/suds/ )  version: 0.3.7 GA  build:
>  R580-20091016
>
>  Service ( ExchangeServices ) tns="
>  http://schemas.microsoft.com/exchange/services/2006/messages"
>     Prefixes (2)
>        ns0 = "http://schemas.microsoft.com/exchange/services/2006/messages"
>        ns1 = "http://schemas.microsoft.com/exchange/services/2006/types"
>     Ports (1):
>        (ExchangeServicePort)
>           Methods (60):
>              AddDelegate(ns1:EmailAddressType Mailbox,
>  ns1:ArrayOfDelegateUserType DelegateUsers, ns1:DeliverMeetingRequestsType
>  DeliverMeetingRequests, )(ns1:NonEmptyArrayOfApplyConversationActionType
>  ConversationActions, )
>  [...]
>  --------
>
>  It seems that indeed there has been a silent error in the consumming of
>  the WSDL.
>
>
>  On Wed, Jun 12, 2013 at 6:04 PM, Matthew Ashton <matthew.ashton3(a)gmail.com
>  > wrote:
>
> > Mathieu, what is the __str__() of the client object you've created? You
> > should be able to see a list of services, ports, methods, and types
> >
> > and Gauthier, I think that question deserves its own thread
> >
> >
> > On Wed, Jun 12, 2013 at 9:17 AM, Gauthier Bastien <gauthier(a)imio.be&gt;wrote:
> >
> >>  Hi,
> >>
> >> we use suds 0.4 in several projects and we could update our package to
> >> use your fork.
> >>
> >> But what I would like to know is, what is the real current state of the
> >> project?  I understand that forking to bitbucket/github and so on is easy,
> >> but is there a plan to make it useable by everybody and what is the current
> >> official repository?
> >>
> >> The current svn seems dead, is it possible to specify on the suds home
> >> page that the code to use is on another repos?  We could even configure
> >> TRAC to display another official repository on bitbucket or any other
> >> source repo...
> >>
> >> I think it would be great because looking at the current state, and last
> >> changes (nothing done for years) make people believe the project is dead,
> >> and maybe it is not the case...
> >>
> >> Thank you and have a nice day,
> >>
> >>    Gauthier Bastien   <http://www.imio.be>
> >> Zoning industriel, 34
> >> 5190 Mornimont
> >> Tél: [phone]
> >> Fax: [phone]
> >> gauthier.bastien(a)imio.be
> >>
> >> La mutualisation informatique
> >> au service des pouvoirs locaux
> >> Le 12/06/13 14:29, Jurko Gospodnetić a écrit :
> >>
> >>   Hi.
> >>
> >> So far I was using a patched version of suds 0.3.7, patched for
> >> dealing better with EWS SOAP (suds-ews :
> >> https://bitbucket.org/daevaorn/suds-ews/). But I don't want to use
> >> that outdated version anymore.
> >>
> >>
> >> I grabbed the last version of suds from pip, the one from jurko which
> >> contains most of the patchs proposed since the development have
> >> stalled, and I have got the following error (I have it too even with
> >> the "regular" suds 0.4.0 release):
> >>
> >>
> >>   In general I suggest using suds-jurko from the sources at the moment.
> >> There have been many fixes & cleanups since the last formal release. For
> >> that matter, I would like to package the current state as the next formal
> >> release, just waiting for some people using it to sent me back a
> >> confirmation that everything is working fine for them.
> >>
> >>   In that versions we've added automated tests checking parts of suds
> >> without having to connect to an external web service, e.g. by using
> >> hardcoded WSDL schemes, injecting fake server responses etc. That code can
> >> now easily be used to reproduce any problematic behaviour without having to
> >> use an externally provided web service. And once you have such a working
> >> locally reproducible test case, you can even change the naming, remove
> >> unnecessary details and such - making both the problem easier to debug and
> >> removing any proprietary information that might have otherwise prevented
> >> you from sending out the code needed to reproduce the problem.
> >>
> >>
> >> I'm really can't figure out what causes the problem. It should work
> >> fine out of the box.
> >> I hope you people of the suds ML can bring some help.
> >>
> >>
> >>   We have not done anything related to EWS there (nor have we ever used
> >> it) so its doubtful your problem has been fixed out-of-the-box.
> >>
> >>   And as for that, if you can let me know how to connect to that web
> >> service, or at least get me the WSDL in question I can take a look at
> >> what's breaking and what workarounds for any of the problems involved have
> >> been made in the patched SOAP version you mentioned. I have not tried out
> >> your code, assuming I'd need some sort of a username & password to make
> it
> >> work.
> >>
> >>
> >>   Best regards,
> >>     Jurko Gospodnetić
> >>
> >> _______________________________________________
> >> suds mailing list
> >> suds(a)lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/suds
> >>
> >>
> >>
> >> _______________________________________________
> >> suds mailing list
> >> suds(a)lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/suds
> >>
> >
> >
> > _______________________________________________
> > suds mailing list
> > suds(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/suds
> >
>
>

[Mathieu Dupuy]

I fear there will be too much differencies between those two revisions of
suds for me to understand what broke what worked before. Additionnaly I
don't know (yet) what files are implied. It's especialy hard since it fails
silently, with no error at all. I'll give a try tomorow.

Yes, I told it in my first mail : I've got the same problem with suds 0.4.0.

On Thu, Jun 13, 2013 at 5:59 PM, Matthew Ashton
<matthew.ashton3(a)gmail.com&gt;wrote:

>  My best guess would be to diff the two version's files to see
> the
>  discrepancies between them when consuming the WSDL..
>
>  it's odd that one would fail and the other would read the file :\
>
>  but have you tried with the newest version of suds? perhaps set up a
>  virtualenv , source bin/activate , install suds 4.0 and see what you get?
>
>
>  On Thu, Jun 13, 2013 at 4:06 AM, Mathieu Dupuy <deronnax(a)gmail.com&gt; wrote:
>
> > This is all I got :
> > --------
> > >>> print str(client)
> > Suds ( https://fedorahosted.org/suds/ )  version: 0.4.1 jurko 5
> > (development)
> >
> > --------
> >
> > Whereas with version I use, I've got a very long list of services :
> > --------
> > Suds ( https://fedorahosted.org/suds/ )  version: 0.3.7 GA  build:
> > R580-20091016
> >
> > Service ( ExchangeServices ) tns="
> > http://schemas.microsoft.com/exchange/services/2006/messages"
> >    Prefixes (2)
> >       ns0 = "http://schemas.microsoft.com/exchange/services/2006/messages
> > "
> >       ns1 = "http://schemas.microsoft.com/exchange/services/2006/types"
> >    Ports (1):
> >       (ExchangeServicePort)
> >          Methods (60):
> >             AddDelegate(ns1:EmailAddressType Mailbox,
> > ns1:ArrayOfDelegateUserType DelegateUsers, ns1:DeliverMeetingRequestsType
> > DeliverMeetingRequests, )(ns1:NonEmptyArrayOfApplyConversationActionType
> > ConversationActions, )
> > [...]
> > --------
> >
> > It seems that indeed there has been a silent error in the consumming of
> > the WSDL.
> >
> >
> > On Wed, Jun 12, 2013 at 6:04 PM, Matthew Ashton <
> > matthew.ashton3(a)gmail.com&gt; wrote:
> >
> >> Mathieu, what is the __str__() of the client object you've created? You
> >> should be able to see a list of services, ports, methods, and types
> >>
> >> and Gauthier, I think that question deserves its own thread
> >>
> >>
> >> On Wed, Jun 12, 2013 at 9:17 AM, Gauthier Bastien <gauthier(a)imio.be&gt;wrote:
> >>
> >>>  Hi,
> >>>
> >>> we use suds 0.4 in several projects and we could update our package to
> >>> use your fork.
> >>>
> >>> But what I would like to know is, what is the real current state of the
> >>> project?  I understand that forking to bitbucket/github and so on is easy,
> >>> but is there a plan to make it useable by everybody and what is the current
> >>> official repository?
> >>>
> >>> The current svn seems dead, is it possible to specify on the suds home
> >>> page that the code to use is on another repos?  We could even configure
> >>> TRAC to display another official repository on bitbucket or any other
> >>> source repo...
> >>>
> >>> I think it would be great because looking at the current state, and
> >>> last changes (nothing done for years) make people believe the project is
> >>> dead, and maybe it is not the case...
> >>>
> >>> Thank you and have a nice day,
> >>>
> >>>    Gauthier Bastien   <http://www.imio.be>
> >>> Zoning industriel, 34
> >>> 5190 Mornimont
> >>> Tél: [phone]
> >>> Fax: [phone]
> >>> gauthier.bastien(a)imio.be
> >>>
> >>> La mutualisation informatique
> >>> au service des pouvoirs locaux
> >>> Le 12/06/13 14:29, Jurko Gospodnetić a écrit :
> >>>
> >>>   Hi.
> >>>
> >>> So far I was using a patched version of suds 0.3.7, patched for
> >>> dealing better with EWS SOAP (suds-ews :
> >>> https://bitbucket.org/daevaorn/suds-ews/). But I don't want to use
> >>> that outdated version anymore.
> >>>
> >>>
> >>> I grabbed the last version of suds from pip, the one from jurko which
> >>> contains most of the patchs proposed since the development have
> >>> stalled, and I have got the following error (I have it too even with
> >>> the "regular" suds 0.4.0 release):
> >>>
> >>>
> >>>   In general I suggest using suds-jurko from the sources at the moment.
> >>> There have been many fixes & cleanups since the last formal release. For
> >>> that matter, I would like to package the current state as the next formal
> >>> release, just waiting for some people using it to sent me back a
> >>> confirmation that everything is working fine for them.
> >>>
> >>>   In that versions we've added automated tests checking parts of suds
> >>> without having to connect to an external web service, e.g. by using
> >>> hardcoded WSDL schemes, injecting fake server responses etc. That code can
> >>> now easily be used to reproduce any problematic behaviour without having to
> >>> use an externally provided web service. And once you have such a working
> >>> locally reproducible test case, you can even change the naming, remove
> >>> unnecessary details and such - making both the problem easier to debug and
> >>> removing any proprietary information that might have otherwise prevented
> >>> you from sending out the code needed to reproduce the problem.
> >>>
> >>>
> >>> I'm really can't figure out what causes the problem. It should work
> >>> fine out of the box.
> >>> I hope you people of the suds ML can bring some help.
> >>>
> >>>
> >>>   We have not done anything related to EWS there (nor have we ever used
> >>> it) so its doubtful your problem has been fixed out-of-the-box.
> >>>
> >>>   And as for that, if you can let me know how to connect to that web
> >>> service, or at least get me the WSDL in question I can take a look at
> >>> what's breaking and what workarounds for any of the problems involved
> have
> >>> been made in the patched SOAP version you mentioned. I have not tried out
> >>> your code, assuming I'd need some sort of a username & password to
> make it
> >>> work.
> >>>
> >>>
> >>>   Best regards,
> >>>     Jurko Gospodnetić
> >>>
> >>> _______________________________________________
> >>> suds mailing list
> >>> suds(a)lists.fedoraproject.org
> >>> https://admin.fedoraproject.org/mailman/listinfo/suds
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> suds mailing list
> >>> suds(a)lists.fedoraproject.org
> >>> https://admin.fedoraproject.org/mailman/listinfo/suds
> >>>
> >>
> >>
> >> _______________________________________________
> >> suds mailing list
> >> suds(a)lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/suds
> >>
> >
> >
>

[Chris Sears]

Have you validated the Soap endpoint using a different client? There's a
nice tool called SoapUI which gives you a graphical interface to explore
and interrogate Soap services. It's generally good to confirm the service's
WSDL is valid and functional before you troubleshoot the Suds client code
too much.

Good luck!
On Jun 13, 2013 12:13 PM, "Mathieu Dupuy" <deronnax(a)gmail.com&gt; wrote:

>  I fear there will be too much differencies between those two
> revisions of
>  suds for me to understand what broke what worked before. Additionnaly I
>  don't know (yet) what files are implied. It's especialy hard since it fails
>  silently, with no error at all. I'll give a try tomorow.
>
>  Yes, I told it in my first mail : I've got the same problem with suds
>  0.4.0.
>
>  On Thu, Jun 13, 2013 at 5:59 PM, Matthew Ashton <matthew.ashton3(a)gmail.com
>  > wrote:
>
> > My best guess would be to diff the two version's files to see the
> > discrepancies between them when consuming the WSDL..
> >
> > it's odd that one would fail and the other would read the file :\
> >
> > but have you tried with the newest version of suds? perhaps set up a
> > virtualenv , source bin/activate , install suds 4.0 and see what you get?
> >
> >
> > On Thu, Jun 13, 2013 at 4:06 AM, Mathieu Dupuy <deronnax(a)gmail.com&gt;wrote:
> >
> >> This is all I got :
> >> --------
> >> >>> print str(client)
> >> Suds ( https://fedorahosted.org/suds/ )  version: 0.4.1 jurko 5
> >> (development)
> >>
> >> --------
> >>
> >> Whereas with version I use, I've got a very long list of services :
> >> --------
> >> Suds ( https://fedorahosted.org/suds/ )  version: 0.3.7 GA  build:
> >> R580-20091016
> >>
> >> Service ( ExchangeServices ) tns="
> >> http://schemas.microsoft.com/exchange/services/2006/messages"
> >>    Prefixes (2)
> >>       ns0 = "
> >> http://schemas.microsoft.com/exchange/services/2006/messages"
> >>       ns1 =
> "http://schemas.microsoft.com/exchange/services/2006/types"
> >>    Ports (1):
> >>       (ExchangeServicePort)
> >>          Methods (60):
> >>             AddDelegate(ns1:EmailAddressType Mailbox,
> >> ns1:ArrayOfDelegateUserType DelegateUsers, ns1:DeliverMeetingRequestsType
> >> DeliverMeetingRequests, )(ns1:NonEmptyArrayOfApplyConversationActionType
> >> ConversationActions, )
> >> [...]
> >> --------
> >>
> >> It seems that indeed there has been a silent error in the consumming of
> >> the WSDL.
> >>
> >>
> >> On Wed, Jun 12, 2013 at 6:04 PM, Matthew Ashton <
> >> matthew.ashton3(a)gmail.com&gt; wrote:
> >>
> >>> Mathieu, what is the __str__() of the client object you've created? You
> >>> should be able to see a list of services, ports, methods, and types
> >>>
> >>> and Gauthier, I think that question deserves its own thread
> >>>
> >>>
> >>> On Wed, Jun 12, 2013 at 9:17 AM, Gauthier Bastien
> <gauthier(a)imio.be&gt;wrote:
> >>>
> >>>>  Hi,
> >>>>
> >>>> we use suds 0.4 in several projects and we could update our package to
> >>>> use your fork.
> >>>>
> >>>> But what I would like to know is, what is the real current state of
> >>>> the project?  I understand that forking to bitbucket/github and so on is
> >>>> easy, but is there a plan to make it useable by everybody and what is
> the
> >>>> current official repository?
> >>>>
> >>>> The current svn seems dead, is it possible to specify on the suds home
> >>>> page that the code to use is on another repos?  We could even configure
> >>>> TRAC to display another official repository on bitbucket or any other
> >>>> source repo...
> >>>>
> >>>> I think it would be great because looking at the current state, and
> >>>> last changes (nothing done for years) make people believe the project is
> >>>> dead, and maybe it is not the case...
> >>>>
> >>>> Thank you and have a nice day,
> >>>>
> >>>>    Gauthier Bastien   <http://www.imio.be>
> >>>> Zoning industriel, 34
> >>>> 5190 Mornimont
> >>>> Tél: [phone]
> >>>> Fax: [phone]
> >>>> gauthier.bastien(a)imio.be
> >>>>
> >>>> La mutualisation informatique
> >>>> au service des pouvoirs locaux
> >>>> Le 12/06/13 14:29, Jurko Gospodnetić a écrit :
> >>>>
> >>>>   Hi.
> >>>>
> >>>> So far I was using a patched version of suds 0.3.7, patched for
> >>>> dealing better with EWS SOAP (suds-ews :
> >>>> https://bitbucket.org/daevaorn/suds-ews/). But I don't want to use
> >>>> that outdated version anymore.
> >>>>
> >>>>
> >>>> I grabbed the last version of suds from pip, the one from jurko which
> >>>> contains most of the patchs proposed since the development have
> >>>> stalled, and I have got the following error (I have it too even with
> >>>> the "regular" suds 0.4.0 release):
> >>>>
> >>>>
> >>>>   In general I suggest using suds-jurko from the sources at the
> >>>> moment. There have been many fixes & cleanups since the last formal
> >>>> release. For that matter, I would like to package the current state as
> the
> >>>> next formal release, just waiting for some people using it to sent me
> back
> >>>> a confirmation that everything is working fine for them.
> >>>>
> >>>>   In that versions we've added automated tests checking parts of
> suds
> >>>> without having to connect to an external web service, e.g. by using
> >>>> hardcoded WSDL schemes, injecting fake server responses etc. That code
> can
> >>>> now easily be used to reproduce any problematic behaviour without having
> to
> >>>> use an externally provided web service. And once you have such a working
> >>>> locally reproducible test case, you can even change the naming, remove
> >>>> unnecessary details and such - making both the problem easier to debug
> and
> >>>> removing any proprietary information that might have otherwise prevented
> >>>> you from sending out the code needed to reproduce the problem.
> >>>>
> >>>>
> >>>> I'm really can't figure out what causes the problem. It should
> work
> >>>> fine out of the box.
> >>>> I hope you people of the suds ML can bring some help.
> >>>>
> >>>>
> >>>>   We have not done anything related to EWS there (nor have we ever
> >>>> used it) so its doubtful your problem has been fixed out-of-the-box.
> >>>>
> >>>>   And as for that, if you can let me know how to connect to that web
> >>>> service, or at least get me the WSDL in question I can take a look at
> >>>> what's breaking and what workarounds for any of the problems involved
> have
> >>>> been made in the patched SOAP version you mentioned. I have not tried
> out
> >>>> your code, assuming I'd need some sort of a username & password
> to make it
> >>>> work.
> >>>>
> >>>>
> >>>>   Best regards,
> >>>>     Jurko Gospodnetić
> >>>>
> >>>> _______________________________________________
> >>>> suds mailing list
> >>>> suds(a)lists.fedoraproject.org
> >>>> https://admin.fedoraproject.org/mailman/listinfo/suds
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> suds mailing list
> >>>> suds(a)lists.fedoraproject.org
> >>>> https://admin.fedoraproject.org/mailman/listinfo/suds
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> suds mailing list
> >>> suds(a)lists.fedoraproject.org
> >>> https://admin.fedoraproject.org/mailman/listinfo/suds
> >>>
> >>
> >>
> >
>
>  _______________________________________________
>  suds mailing list
>  suds(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds
>

[Jurko Gospodnetić]

   Hi.

On 12.6.2013. 16:17, Gauthier Bastien wrote:
>  we use suds 0.4 in several projects and we could update our package
> to
>  use your fork. 
   Glad to hear it. Especially if you have a test suit for your projects 
that could help detect any breakage caused by the changes in the fork. :-)

   The original project did not have a solid enough stand-alone test 
suite to make me feel free to fix things 'on impulse' or package the 
current results as a formal release without additional external 
confirmation that 'everything works ok'.


>  But what I would like to know is, what is the real current state of
> the
>  project?  I understand that forking to bitbucket/github and so on is
>  easy, but is there a plan to make it useable by everybody and what is
>  the current official repository? 
   I'll post more info on my fork in a separate thread but it is public, 
and should be usable by everybody as it is now. :-)

   You can get it from pypi (manually or using easy-install or pip or 
whatever...) or from the project hosted on BitBucket directly. Although 
admittedly, the last packaged release is now a year old so my suggestion 
would be to use the source-based version from BitBucket.

   But let's move to the other thread if you want to continue with this 
topic...

   Best regards,
     Jurko Gospodnetić

[Gauthier Bastien]

Hi,

I will test with 2 projects where, fortunately, a requirement we set was 
a test coverage of 100% ;-)

For now, suds 0.4 pass the test, it is not a question of using another 
version because we have problems, it is just a question of relying on 
sustainable packages...

I added a ticket to our work tracker to test this, I will come back to 
you when I will have had the time to do it.

We use it with Zope 2.13/z3c.soap/ZSi/suds/Plone 4.x for information.

We should probably try to contact the original maintener and expose him 
this thread ;-)

Have a nice day,

Gauthier Bastien
<http://www.imio.be>
Zoning industriel, 34
5190 Mornimont
Tél: [phone]
Fax: [phone]
gauthier.bastien(a)imio.be <mailto:[e-mail]>
	
La mutualisation informatique
au service des pouvoirs locaux

Le 13/06/13 13:05, Jurko Gospodnetić a écrit :
>    Hi.
>
>  On 12.6.2013. 16:17, Gauthier Bastien wrote:
> > we use suds 0.4 in several projects and we could update our package to
> > use your fork.
>
>    Glad to hear it. Especially if you have a test suit for your 
>  projects that could help detect any breakage caused by the changes in 
>  the fork. :-)
>
>    The original project did not have a solid enough stand-alone test 
>  suite to make me feel free to fix things 'on impulse' or package the 
>  current results as a formal release without additional external 
>  confirmation that 'everything works ok'.
>
>
> > But what I would like to know is, what is the real current state of the
> > project?  I understand that forking to bitbucket/github and so on is
> > easy, but is there a plan to make it useable by everybody and what is
> > the current official repository?
>
>    I'll post more info on my fork in a separate thread but it is 
>  public, and should be usable by everybody as it is now. :-)
>
>    You can get it from pypi (manually or using easy-install or pip or 
>  whatever...) or from the project hosted on BitBucket directly. 
>  Although admittedly, the last packaged release is now a year old so my 
>  suggestion would be to use the source-based version from BitBucket.
>
>    But let's move to the other thread if you want to continue with this 
>  topic...
>
>    Best regards,
>      Jurko Gospodnetić
>
>  _______________________________________________
>  suds mailing list
>  suds(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds

[Jurko Gospodnetić]

   Hi.

On 12.6.2013. 15:18, Mathieu Dupuy wrote:
>  I tried anew with the suds' trunk version, 0.4.1-5-soon-to-be and
> the
>  problem reproduces.
>  Of course I don't have the ability to give you access or account to
>  the server, so here is joined to this mail the schema files of EWS,
>  including the WSDL file. Ask if you need anything else. 
[Mathieu, I'm sending this reply back to the mailing list even though 
you directed the original question directly to me so you could possibly 
get more useful feedback from others.]

   Ok, I took a look at this now.

   FYI, you can reproduce the behaviour you saw without using an 
external service and without having to provide anyone with any usernames 
& passwords by using the following code with the suds-jurko fork:

>  import suds
>  import suds.client
>  import suds.store
>
>  wsdl_xml = suds.byte_str("""...XML from
> http://www.w3.org/2001/xml.xsd...""")
>  wsdl_messages = suds.byte_str("""...XML from
> Messages.xsd...""")
>  wsdl_types = suds.byte_str("""...XML from Types.xsd...""")
>  wsdl_services =  suds.byte_str("""...XML from
> Services.wsdl...""")
>
>  store = suds.store.DocumentStore({'messages.xsd':wsdl_messages,
>      'services.wsdl':wsdl, 'types.xsd':wsdl_types,
>      'www.w3.org/2001/xml.xsd':wsdl_xml})
>  client = suds.client.Client("suds://services.wsdl", cache=None,
>      documentStore=store, nosend=True) 
   All WSDL/XSD schema files are stored in the DocumentStore object and 
suds Client just fetches them from there instead of attempting to fetch 
them over the net. It does not matter if you hardcode the file content 
or read it from an external file or whatever. It only matters that the 
content seen by the suds Client is a byte string and its content encoded 
using utf-8 encoding.

   I did this and truely, suds does not recognize any services from the 
WSDL you sent me.

   I took a look at the WSDL itself and there really are no 
<wsdl:service> elements defined there.

   I am not versed enough in the standard to know if this is even legal 
or how this WSDL should be interpreted. I'll take a look at what that 
other fork you mentioned does in this case when I find some more free 
time - most likely not before the the weekend.

   Any further research you or someone else can do or feedback you can 
provide on this would help though. ;-)

   Best regards,
     Jurko Gospodnetić

[Jurko Gospodnetić]

   Hi.

>     I did this and truely, suds does not recognize any services from
> the
>  WSDL you sent me.
>
>     I took a look at the WSDL itself and there really are no
>  <wsdl:service> elements defined there. 
   I tried adding a valid <wsdl:service> tag into Messages.wsdl as follows:

>      <wsdl:service name="ExchangeServices">
>          <wsdl:port name="ExchangeServicePort"
> binding="tns:ExchangeServiceBinding">
>              <soap:address location="http://bla-bla"/>
>          </wsdl:port>
>      </wsdl:service> 
   Afterwards suds-jurko seems to have correctly recognized the WSDL 
content. Printing out the Client object then as a string prints out lots 
of method & type names.

   Give that a try and see how it works on your end.

   Best regards,
     Jurko Gospodnetić

[Mathieu Dupuy]

Hi.
Of course I forgot the reply-all. I had a google labs gmail feature
that used to make reply-all automatic but google silently removed it.
Silly google.
You wrote "add this snippet in Messages.wsdl", since there is no file
named like this, I first add it to "Messages.xsd", it didn't work, and
I switched to another tasks, thinking your fix didn't work. This
morning I add it to "Services.wsdl" and indeed it worked, I add the
list of methods. But I can't manage to get suds using my local
Services.wsdl and and talking to the exchange soap server. I'm
currently very new to soap and suds, and I would need some help. When
I change the url "suds://services.wsdl" the online wsdl, it falls back
on "no service defined". I'm sure there are options for telling suds
to connect to the server and use the local wsdl file all togethet, but
I can't spend more time on this. I joined a pastebin with my attempts
: http://bpaste.net/show/107868/. Thank you very much.


I took a look to the diff between suds 0.3.7 and ews-suds-0.3.7, and
the guy made an amazing work. I contacted him to ask if he was willing
to port it to the last version of suds, which I don't think he will,
and if he won't, I'll give a try to forward port the modifications to
the development version of suds. If you agree, I'll be happy to submit
the patch in order you to integrate it. Amongst those modifications,
there is one for supporting wsdl file with no wsdl:service tags.

@Chris : i installed soapUi : it was clumsy, buggy (it considers that
path are case insensitive by default, so it works poorly on Linux) and
very unclear. Since i could not manage to do somethinh with it in
little time, I didn't strive further).

On Thu, Jun 13, 2013 at 11:39 PM, Jurko Gospodnetić
<jurko.gospodnetic(a)pke.hr&gt; wrote:
>    Hi.
>
>
> >    I did this and truely, suds does not recognize any services from the
> > WSDL you sent me.
> >
> >    I took a look at the WSDL itself and there really are no
> > <wsdl:service> elements defined there.
>
>
>    I tried adding a valid <wsdl:service> tag into Messages.wsdl as follows:
>
> >     <wsdl:service name="ExchangeServices">
> >         <wsdl:port name="ExchangeServicePort"
> > binding="tns:ExchangeServiceBinding">
> >             <soap:address location="http://bla-bla"/>
> >         </wsdl:port>
> >     </wsdl:service>
>
>
>    Afterwards suds-jurko seems to have correctly recognized the WSDL content.
>  Printing out the Client object then as a string prints out lots of method &
>  type names.
>
>    Give that a try and see how it works on your end.
>
>
>    Best regards,
>      Jurko Gospodnetić
>
>  _______________________________________________
>  suds mailing list
>  suds(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/suds

[Jurko Gospodnetić]

   Hi.

>  You wrote "add this snippet in Messages.wsdl", since there
> is no file
>  named like this, I first add it to "Messages.xsd", it didn't work, and
>  I switched to another tasks, thinking your fix didn't work. This
>  morning I add it to "Services.wsdl" and indeed it worked, I add the
>  list of methods. But I can't manage to get suds using my local
>  Services.wsdl and and talking to the exchange soap server. I'm
>  currently very new to soap and suds, and I would need some help. When
>  I change the url "suds://services.wsdl" the online wsdl, it falls back
>  on "no service defined". I'm sure there are options for telling suds
>  to connect to the server and use the local wsdl file all togethet, but
>  I can't spend more time on this. 
   Actually, if you have a correct WSDL locally, simply using that one 
will fix your problem. You can do it using the DocumentStore class, as 
done in existing test code, or you can store the file on disk and 
reference it using the 'file://host/path' URL.

   Just make sure the WSDL in question points to the correct web service 
host address & port.


>  I took a look to the diff between suds 0.3.7 and ews-suds-0.3.7, and
>  the guy made an amazing work. I contacted him to ask if he was willing
>  to port it to the last version of suds, which I don't think he will,
>  and if he won't, I'll give a try to forward port the modifications to
>  the development version of suds. If you agree, I'll be happy to submit
>  the patch in order you to integrate it. Amongst those modifications,
>  there is one for supporting wsdl file with no wsdl:service tags. 
   Yeah, I also took a look at that fork, and someone did do some work 
there, but the changes are not generic. E.g. the 'missing wsdl:service 
tag workaround' simply fakes having such a tag by assuming it is talking 
to an Exchange server - not really generic enough. I'd be happier if an 
optional workaround was added that would do something like this:
   1. if there are no ports defined - error out
   2. if there are any ports defined - fake a service entity without a 
valid host address connected to all the listed ports.
   3. using such a web service would require that the client explicitly 
specify the target server address before making any calls on it.

   There are also some other patches there, but I do not really have any 
way to test what they fix, so you'll have to take the time and do some
heavy lifting if you want such changes integrated into suds-jurko.


>  @Chris : i installed soapUi : it was clumsy, buggy (it considers
> that
>  path are case insensitive by default, so it works poorly on Linux) and
>  very unclear. Since i could not manage to do somethinh with it in
>  little time, I didn't strive further). 
   SoapUI is a great tool on Windows. Sometimes a bit buggy/flaky, but 
generally works fine.


   Best regards,
     Jurko Gospodnetić