-
Logged In: YES
user_id=88162
Thank you -- I grabbed the latest code from CVS and it
solved my problem.
2006-02-08 14:49:44 UTC in Web Services for Python
-
Logged In: YES
user_id=88162
I'm new to SOAP, but I take it from your response that this
part of the WSDL, which does refer to the non-standard
response name "OAMCommandExecResult," isn't relevant:
Service definition of function
SoapOAM__getOM
2006-02-03 21:04:46 UTC in Web Services for Python
-
Logged In: YES
user_id=88162
I'm sorry, I accidentally pasted the lines in the wrong
order above. The second line (with
"executeCommandResponse") is what wsdl2py generated, as you
confirmed. The first line (with "OAMCommandExecResult"
instead) is what I had to edit it to in order to get it to
work. These is still a bug in there, I just described it wrong.
2006-02-03 19:29:38 UTC in Web Services for Python
-
I used wsdl2py from ZSI-2.0-rc1 and I wound up having
to make a modification to the generated services.py
file in order to use the web service. I had to edit
the line:
OAMCommandExecResult.typecode =
Struct(pname=("urn:SoapOAM","OAMCommandExecResult"),
ofwhat=[ZSI.TC.Boolean(pname="m-bExecSuccess",
aname="_m_bExecSuccess", encoded=None, minOccurs=1,
maxOccurs=1, nillable=True)...
2006-02-02 16:31:55 UTC in Web Services for Python
-
You are right! It was the JythonInterpreter plugin version 0.9.6 that was conflicting. Once I removed that plugin, everything worked correctly.
Thanks for all your help.
2005-05-12 22:06:08 UTC in jpydbg
-
Yup, I have just one copy of inspector.py.
This all works exactly the same way on a co-worker's machine -- the syntax checking only works if you un-check and re-check JPyDebug. So it's not just me... there must be something different about our configuration.
2005-05-12 21:54:28 UTC in jpydbg
-
I only have 1 copy of jpydebug.jar on my whole machine, so there's no way I could have 2 versions installed.
I'm using SideKick 0.3.3.
2005-05-12 21:10:23 UTC in jpydbg
-
I just found a way to make the syntax checking work -- I go to the Plugin Manager, un-check the box next to JPyDebug, and re-check it. Then the syntax checking works!
Unfortunately, if I close and reopen JEdit, it isn't working again. I have to repeat the same un-check, re-check sequence in the Plugin Manager in order to get it to work, every time I start up JEdit.
2005-05-12 17:36:46 UTC in jpydbg
-
I do have a full path there. It really looks to me that inspector.py isn't getting called at all. I added this to the top of the file:
import time
f = open(r'c:\junk\junk.debug', 'a')
f.write('%s: inspector.py loaded\n' % time.time())
f.flush()
f.close()
del f
When I run inspector.py from the command line, an output line shows up in c:\junk\junk.debug. But when I start up JEdit...
2005-05-12 15:49:38 UTC in jpydbg
-
I'm running Windows 2000. I do have a temp directory configured properly.
I just noticed that if I have the sidekick Structure Browser open, the structure tree does show up in there when I save. Is that created by inspector.py also?.
2005-05-12 15:20:08 UTC in jpydbg
