Path: csiph.com!usenet.pasdenom.info!gegeweb.org!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <514DAF1D.50801@googlemail.com>
References: <514A0898.4000807@googlemail.com> <CAPTjJmoWL0B1OSj2MrLWfQF_0znVrggjcFhY7crAoYZRkcpEbQ@mail.gmail.com> <514DAF1D.50801@googlemail.com>
Date: Sun, 24 Mar 2013 02:03:57 +1100
Subject: Re: SOAPpy.Types.faultType: Cannot use object of type stdClass as array
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.3639.1364051041.2939.python-list@python.org>
Lines: 57
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:41736

On Sun, Mar 24, 2013 at 12:33 AM, Tamer Higazi <th982a@googlemail.com> wrote:
> Hi Chris!
> thanks.... But I am about of going nuts.... I did everything according
> their sample:
>
> http://kasapi.kasserver.com/dokumentation/?open=soap

Since I'm not fluent in German, I'm relying on Google Translate to
read of that page. (I didn't find an obvious English version of the
page, but maybe I just didn't look in the right place.)

One thing I've found about the PHP SOAP library is that it seems to
behave quite oddly in some circumstances - my suspicion is the WSDL
file (eg when it's unable to load it). Try monitoring the actual
traffic - SOAP is XML carried over HTTP, so you should be able to just
snoop the TCP/IP socket (easiest way might be to switch in your own
server). See if you can spot a difference between the request that PHP
sends and the one your Python script sends. Fortunately you're not
moving megabytes of data around, here - it should be easy enough to
eyeball the requests and see what's different about them :)

A tip, by the way:

        userpass = ['login','password']
        m = hashlib.sha1()
        m.update(userpass[1])

        userpass[1] = m.hexdigest()
        loginData = {'user':userpass[0],'pass':userpass[1]}

                'KasUser':loginData['user'],
                'KasPassword':loginData['pass'],

You keep packaging and repackaging the credentials. I'm assuming you
won't actually have them hard-coded like that (if you do, I would
recommend hard-coding the SHA1 hash, rather than the password itself),
so I'll stick with the userpass list (or tuple, which would work
exactly the same way).

password = hashlib.sha1(userpass[1]).hexdigest()
...
                'KasUser':userpass[0],
                'KasPassword':password,

Or even inline that completely (which is what I'd probably do).
There's no need to stuff it into a dictionary, only to pull it out
again.

Also: A try/except that just prints out the error message usually
isn't helpful. Save yourself the trouble, at least during initial
testing - just let the exception terminate your script. You'll get all
the same information, plus the full traceback, and it's cost you
exactly zero development time :) Later on, you can add try/except if
you need to do something other than terminate, but often that "later
on" never even happens.

ChrisA