在python中处理SOAP类型异常的最佳方法是什么

时间:2011-09-23 13:29:07

标签: python xml soap

如果用户输入的数据不在WSDL访问的Web服务器上,我会收到错误:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:ns3="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
   <SOAP-ENV:Header/>
   <ns2:Body>
      <ns1:getFieldsForEdit>
         <in0 xsi:type="ns3:string">FmofSimScl</in0>
         <in1 xsi:type="ns3:string">QA-65000</in1>
      </ns1:getFieldsForEdit>
   </ns2:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:ns3="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
   <SOAP-ENV:Header/>
   <ns2:Body>
      <ns1:getIssue>
         <in0 xsi:type="ns3:string">FmofSimScl</in0>
         <in1 xsi:type="ns3:string">QA-65000</in1>
      </ns1:getIssue>
   </ns2:Body>
</SOAP-ENV:Envelope>
Traceback (most recent call last):
  File "/home/qa/jira-test/.hg/check_jira.py", line 64, in <module>
    main()
  File "/home/qa/jira-test/.hg/check_jira.py", line 12, in main
    commit_text_verified = verify_commit_text(os.popen('hg tip --template "{desc}"'))
  File "/home/qa/jira-test/.hg/check_jira.py", line 35, in verify_commit_text
    if CheckForJiraIssueRecord(m_args) == 0:
  File "/home/qa/jira-test/.hg/check_jira.py", line 58, in CheckForJiraIssueRecord
    issue = com.run(command_name, logger, jira_env, my_args)
  File "/home/qa/jira-test/.hg/jira.py", line 1367, in run
    return self.commands[command].dispatch(logger, jira_env, args)
  File "/home/qa/jira-test/.hg/jira.py", line 75, in dispatch
    results = self.run(logger, jira_env, args)
  File "/home/qa/jira-test/.hg/jira.py", line 174, in run
    logger.error(decode(e))
  File "/home/qa/jira-test/.hg/jira.py", line 1434, in decode
    str = e.faultstring
AttributeError: 'WebFault' object has no attribute 'faultstring'
transaction abort!
rollback completed
abort: pretxncommit.jira hook exited with status 1

有没有办法处理这个问题,所以我可以编写自己的错误字符串或警告消息而不是所有这些。如果我关闭stdout我没有得到xml数据,但我仍然得到:

transaction abort!
rollback completed
abort: pretxncommit.jira hook exited with status 1

来自mercurial,但很高兴有一个附加到它的错误字符串 warnings.warn(&#34;%s不存在&#34;%issue_id)

好吧,我看着jira.py 并在第1434行更改: str = e.faultstring 至 str = e.fault

得到了:

faultcode = "soapenv:Server.userException"
   faultstring = "com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it."
   detail = 
      (detail){
         com.atlassian.jira.rpc.exception.RemotePermissionException = ""
         hostname = "JIRA"
      }
 }

1 个答案:

答案 0 :(得分:1)

它已在jira.py中修复: 将解码功能更改为:


def decode(e):
    """Process an exception for useful feedback"""
    # TODO how to log the fact it is an error, but allow info to be unchanged?
    # TODO now fault not faultstring?
    # The faultType class has faultcode, faultstring and detail
    str = e.fault
    if str == 'com.atlassian.jira.rpc.exception.RemotePermissionException':
        return "This issue does not exist or you don't have permission to view it"
    return e.fault

而不是:


def decode(e):
    """Process an exception for useful feedback"""
    # TODO how to log the fact it is an error, but allow info to be unchanged?
    # TODO now fault not faultstring?
    # The faultType class has faultcode, faultstring and detail
    str = e.faultstring
    if str == 'java.lang.NullPointerException':
        return "Invalid issue key?"
    return e.faultstring