March 2010 - suds - Fedora Mailing-Lists

by Martin Aspeli

Hi, I've been hacking up a little package that uses Suds' WSDL parsing to generate Python code that describes the service and its complex types using zope.interface semantics. This helps us in creating mocks for our remote SOAP service. The code generator is here: http://bitbucket.org/optilude/wsdl2interface/src/tip/wsdl2interface.py ; if you want to test it, it's on PyPI: http://pypi.python.org/pypi/wsdl2interface I'm getting quite confused by two things, though, probably because the internal Suds data structures are so comprehensive: - I'd like to output (as a comment) the return type for each method in the service interface. The 'print client' output doesn't have this. Any clues on where I should look? - In the WSDL file from our supplier, we seem to be getting one complex type for each service method. For example, we have 'addFavorite' as a complex type and 'addFavorite()' as a method. The method takes the same arguments as the complex type. In some other test services I used, that didn't happen. It may just be that I'm mis-understanding something about SOAP, but can you shed some light on why it's coming out like this, and whether I should be trying to filter out these types somehow? Any hints? Our WSDL file looks a bit like this (snipped and obfuscated slightly): {{{ <definitions name='AcmeServiceBeanService' targetNamespace=' http://ejb3.acme.boo.example.com/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns=' http://ejb3.acme.boo.example.com/' xmlns:xsd=' http://www.w3.org/2001/XMLSchema'> <types> <xs:schema targetNamespace='http://ejb3.acme.boo.example.com/' version='1.0' xmlns:tns='http://ejb3.acme.boo.example.com/' xmlns:xs=' http://www.w3.org/2001/XMLSchema'> <xs:element name='addFavourite' type='tns:addFavourite'/> <xs:element name='addFavouriteResponse' type='tns:addFavouriteResponse'/> <xs:complexType name='addFavourite'> <xs:sequence> <xs:element minOccurs='0' name='tokenId' type='xs:string'/> <xs:element name='favoriteId' type='xs:short'/> <xs:element minOccurs='0' name='favoriteName' type='xs:string'/> </xs:sequence> </xs:complexType> <xs:complexType name='addFavouriteResponse'> <xs:sequence> <xs:element name='response' type='xs:int'/> </xs:sequence> </xs:complexType> </xs:schema> </types> <message name='AcmeServiceBean_addFavouriteResponse'> <part element='tns:addFavouriteResponse' name='addFavouriteResponse'></part> </message> <message name='AcmeServiceBean_addFavourite'> <part element='tns:addFavourite' name='addFavourite'></part> </message> <portType name='AcmeServiceBean'> <operation name='addFavourite' parameterOrder='addFavourite'> <input message='tns:AcmeServiceBean_addFavourite'></input> <output message='tns:AcmeServiceBean_addFavouriteResponse'></output> </operation> </portType> <binding name='AcmeServiceBeanBinding' type='tns:AcmeServiceBean'> <soap:binding style='document' transport=' http://schemas.xmlsoap.org/soap/http'/> <operation name='addFavourite'> <soap:operation soapAction=''/> <input> <soap:body use='literal'/> </input> <output> <soap:body use='literal'/> </output> </operation> </binding> <service name='AcmeServiceBeanService'> <port binding='tns:AcmeServiceBeanBinding' name='AcmeServiceBeanPort'> <soap:address location='http://127.0.0.1:8080//AcmeService'/> </port> </service> </definitions> }}} The Suds client looks like this: {{{ Suds ( https://fedorahosted.org/suds/ ) version: 0.3.9 GA build: R659-20100219 Service ( AcmeServiceBeanService ) tns="http://ejb3.acme.boo.example.com/" Prefixes (1) ns0 = "http://ejb3.acme.boo.example.com/" Ports (1): (AcmeServiceBeanPort) Methods (1): addFavourite(xs:string tokenId, xs:short favoriteId, xs:string favoriteName, ) Types (2): addFavourite addFavouriteResponse }}} When I run the code generator, the output is: {{{ from zope.interface import Interface, Attribute from zope import schema class IAddFavourite(Interface): """SOAP complex type ``{http://ejb3.acme.boo.example.com/}addFavourite`` """ tokenId = schema.TextLine(description=u"WSDL type: string") favoriteId = schema.Int(description=u"WSDL type: short") favoriteName = schema.TextLine(description=u"WSDL type: string") class IAddFavouriteResponse(Interface): """SOAP complex type ``{http://ejb3.acme.boo.example.com/}addFavouriteResponse`` """ response = schema.Int(description=u"WSDL type: int") WSDL_TYPES = { 'addFavourite': IAddFavourite, 'addFavouriteResponse': IAddFavouriteResponse } class IAcmeServiceBeanService(Interface): """SOAP service ``AcmeServiceBeanService`` with target namespace http://ejb3.acme.boo.example.com/. """ def addFavourite(tokenId, favoriteId, favoriteName): """Parameters: ``tokenId`` -- string (optional) ``favoriteId`` -- short ``favoriteName`` -- string (optional) """ }}} Thanks, Martin

14 years, 1 month

1
0
0 / 0

Problem with complexType / sequence / choice structure.

by Kuosa, Jussi

Hello all, I'm having a problem while trying to consume a web service with suds 0.3.8. The majority of the operations are parsed correctly and I'm able to call them (with WSS and custom headers). However, I seem to have a problem with a particular WSDL construct: <xsd:element name="enableXxxRequest"> <xsd:complexType> <xsd:sequence> <xsd:choice> <xsd:element name="xxxIdentifier" type="xsd:string" maxOccurs="1" minOccurs="1"/> <xsd:element name="xxxYyyReference" type="xsd:string" maxOccurs="1" minOccurs="1"/> </xsd:choice> </xsd:sequence> </xsd:complexType> </xsd:element> If I print the generated client, I only get enable() without any indication on how to generate the proper call. I guess that I have to somehow indicate whether I'm passing in an xxxIdentifier or xxxYyyReference and then just put them in a list (like result = client.service.enable([id1, id2]))? I tried creating id1 = Element("xxxIdentifier").setText("some identifier"), but that wasn't put to the request. Can anyone help me out? Best regards, Jussi Kuosa

14 years, 1 month

1
0
0 / 0

Proxy Problems

by dunkel gruen

Hello, in my las mail i ask for a look at the xml request. I find the logging and could fix it. Thanks! Now i have a litte nice python programm ready to use with a webservice. :) Today i try to use it in a enviroment with a proxy. I read the examples and try and try but i'm not sure that the code is right. At least i get no connection... Here is a short example that dosn't work... #!/usr/bin/python #-*- coding: utf-8 -*- import suds url = "http://www.thomas-bayer.com/axis2/services/BLZService?wsdl<https://mailgate.roc-berlin.de/exchweb/bin/redir.asp?URL=http://www.thoma...> " d = dict(http='192.168.50.2:3129') client = client.set_options(proxy=d) print suds.client.Client(url) Can you send me a correct example? dunkelgruen

14 years, 1 month

2
2
0 / 0

assur ers shinn y packe rs

by Buy C1alis on www.hg67.net

surge oncy croci dolit e detec ting bicon vexit y grand maste r repla ying docil ely unlin ks signi or modic ity swart z morib und yaup vibra nt dedic ating liter alize r morib und egoce ntric docil ely vestr yise varsi ty tempe rate awlwo rt quixo tical cinch es ashe ocean s badne ss topcr oss shock stall boome r socio metry jabbe rings packe rs arris es scari fy boler o catal ysers blanc yaup gonor rheal camio n derog ated undec illio n lalla ns bellw ether s accos t disfa vorer s sense lordl ier pimpi ng bouva rdier rocko on varsi ty recip rocal s fribb ling downw eight ed boil regio nalis ed trail ed snuff box gaekw ar fibro cemen t tung compa ssed menst ruati on faggi ng choki ngly areal caten ary

14 years, 1 month

1
0
0 / 0

Using unbound type

by Philippe Gauvin :: Magnet Média

Hi, I have the following client definition. Suds ( https://fedorahosted.org/suds/ ) version: 0.4 (beta) build: > R663-20100303 > Service ( MeetingSpaceProviderService ) tns=" > http://htng.org/PWSWG/2007/01/DigitalSignage" Prefixes (2) ns0 = " > http://htng.org/PWSWG/2007/01/DigitalSignage/MeetingSpaceRequest/Types" ns1 = " > http://htng.org/PWSWG/2007/01/DigitalSignage/MeetingSpaceResponse/Types" Ports (2): (MeetingSpaceServiceSoap) Methods (2): MeetingSpaceCharacteristicsRequest() MeetingSpaceRequest(ns0:DateRange DateRange, ) Types (6): ns1:EventType ns1:GroupType ns1:MeetingSpaceType ns1:OtherRoomType ns1:PropertyType ns1:SubMeetingSpaceType (MeetingSpaceServiceSoap1) Methods (2): MeetingSpaceCharacteristicsRequest() MeetingSpaceRequest(ns0:DateRange DateRange, ) Types (6): ns1:EventType ns1:GroupType ns1:MeetingSpaceType ns1:OtherRoomType ns1:PropertyType ns1:SubMeetingSpaceType I need to call the MeetingSpaceCharacteristicsRequest like this <soap:Body> <MeetingSpaceCharacteristicsRequest propertyKey="3917" xmlns=" > http://htng.org/PWSWG/2007/01/DigitalSignage/MeetingSpaceCharacteristicsR..." > /> </soap:Body> but because propertyKey is not a listed type. I am not sure how to proceed. I have tried binding the xsd manually (propertyKey is a defined type in the xsd) but no luck. from suds.xsd.sxbasic import Import ns = ' > http://htng.org/PWSWG/2007/01/DigitalSignage/MeetingSpaceCharacteristicsR... > ' location = ' > http://htng.org/PWSWG/2007/01/DigitalSignage/MeetingSpaceCharacteristicsR... > ' Import.bind(ns, location) First time fiddling with soap, so sorry if the question is easy and hopefully it is ;-) Phil

14 years, 1 month

1
1
0 / 0

How can i have a look to the sending XML

by Sebastian Preuß

Hello, today i had a first nice try with suds. Know i have Authentication problems to log in at my webservice. How can i have a look to the xml that suds sends to fix problems. Thanks dunkelgruen

14 years, 2 months

2
1
0 / 0

(no subject)

by Curpupoz Shall

14 years, 2 months

1
0
0 / 0

Re: [Fedora-suds-list] Question about WSSE

by Frank Millman

Jeff Ortel wrote: > > Your suggestion makes sense and I will happily change it but > I'm concerned that it will break existing WSSE users. I'll > post a specific RFC for this change on the list. > Thanks, Jeff. I quite agree about existing users - let's see what they say. To save you looking up the spec, here are a couple of relevant extracts. 1. 'A nonce is a random value that the sender creates to include in each UsernameToken that it sends.' The current method in suds of contructing a nonce is a bit involved. According to the spec, it can be any random string. 2. The Password element should have a Type attribute, which is one of the following - #PasswordText (default) The actual password for the username, the password hash, or derived password or S/KEY. This type should be used when hashed password equivalents that do not rely on a nonce or creation time are used, or when a digest algorithm other than SHA1 is used. #PasswordDigest The digest of the password (and optionally nonce and/or creation timestame) for the username using the algorithm described above. I am no expert, so I am not sure of the significance of the '#' symbol. In an example, it shows the following - <wsse:Password Type="...#PasswordDigest"> weYI3nXd8LjMNVksCKFV8t3rgHh3Rw== </wsse:Password> Elsewhere in the document, it refers to 'wsse:PasswordText' and 'wsse:PasswordDigest'. So personally I am not sure what it is supposed to look like, but hopefully you can make more sense of this. Thanks Frank

14 years, 2 months

1
0
0 / 0

how to use Suds on Google App Engine?

by Jacob Gur

I am seeing an error trying to implement Suds on Google App Engine (GAE), because Suds wants to cache the WSDL bindings to temporary files, whereas GAE does not allow file writing. How do I pre-generate the bindings that Suds needs, or make Suds cache in memory? I tried setting cache=None, but it looks like it still is trying to generate those files. Does anyone have samples and instruction how to use Suds on GAE? Thanks! Jacob

14 years, 2 months

1
0
0 / 0

I have a list of 160k dentists in the US

by norway Baker

Email me at this address for a catalog of all our US lists: Tisha.Clement(a)therightlist.Co.CC Also, ask about our sale pricing for more than one list. Send us an email to rembox(a)therightlist.Co.CC we will discontinue from the list

14 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

suds March 2010