I'm calling a PythonScript via xmlrpc and an error is being returned that includes HTML with the error type and value but no stack trace. I've no idea if this is correct behaviour or a bug or a misconfiguration but it's really annoying me as I have no idea how to reproduce the error inside zope where I do get stack traces. The zope instance is running on w2k with -D option and I get stack traces in the HTML with normal webrequests (assuming they cause an exception). Is this a bug or what?
Jay, Dylan writes:
I'm calling a PythonScript via xmlrpc and an error is being returned that includes HTML with the error type and value but no stack trace. I've no idea if this is correct behaviour or a bug or a misconfiguration but it's really annoying me as I have no idea how to reproduce the error inside zope where I do get stack traces. The zope instance is running on w2k with -D option and I get stack traces in the HTML with normal webrequests (assuming they cause an exception). Call your PythonScript via HTTP (instead of XML-RPC). This can look something like:
<http://<your-Zope>/<PathToTheScript>?param1=value1¶m2=value2&... You may need urlencoding and form variables converters to get the correct values to the script. If this is two complex, make a specialized Python Script, that calls your Python script with the correct arguments. Call this Python Script via HTTP. Dieter
participants (2)
-
Dieter Maurer -
Jay, Dylan