blocks|key|2348279|text|简而言之，Suds不支持SOAP+1.2绑定。开发已经停止了很长一段时间。由于这个原因，SudsLibrary也不支持它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2348280|我使用example+service+SOAP+1.1/1.2观察到的一些差异是：|offset|length|2348281|2348282|+header+Content-Type：|ordered-list-item|style|CODE|2348283|1.2+=+"application/soap%2Bxml"+|unordered-list-item|2348284|1.1+=+"text/xml".|2348285|2348286|2348287|​|2348288|2348289|+header+|2348290|1.2+=+Action+|2348291|1.1+=+SOAPAction|2348292|2348293|2348294|2348295|2348296|Envelope+Namespace+|2348297|1.2+=+"http://www.w3.org/2003/05/soap-envelope"+|2348298|1.1+=+"http://schemas.xmlsoap.org/soap/envelope/"|2348299|2348300|2348301|2348302|对于其中的每一个，在下面的示例中都实现了一个单独的解决方案。内容类型可能会被覆盖。可以添加操作，但不能删除SOAPAction。也可以使用扩展库覆盖命名空间。如果您的服务忽略SOAPaction标头属性，这应该适用于您。|2348303|测试Case.robot|BOLD|2348304|***+Settings+***
Library++++SudsLibrary
Library++++SudsLibraryExtension
Library++++Collections++++

***+Test+Cases+***
TC
++++${BASE_URL}++++Set+Variable+++++++++http://www.holidaywebservice.com
++++${SERVICE}+++++Create+Dictionary++++
++++...+++++++++++++++++++++++++++++++++name=HolidayService_v2++++
++++...+++++++++++++++++++++++++++++++++wsdl=HolidayService2.asmx?WSDL
++++${PORT}++++++++Set+variable+++++++++HolidayService2Soap12
++++${METHOD}++++++Set+variable+++++++++GetCountriesAvailable

++++Set+Binding+++++SOAP-ENV++++http://www.w3.org/2003/05/soap-envelope
++++Create+Soap+Client+++++${BASE_URL}/${SERVICE.name}/${SERVICE.wsdl}
++++Set+Port++++${PORT}

++++Set+Headers++++Content-Type++++application/soap%2Bxml
++++Set+Headers++++Soapaction++++++${EMPTY}
++++Set+Headers++++Action++++++++++"${BASE_URL}/${SERVICE.name}/${METHOD}"

++++${result}++++++++++Call+Soap+Method+++++${METHOD}|code-block|syntax|javascript|2348305|SudsLibraryExtension.py|2348306|import+suds.bindings
from+robot.libraries.BuiltIn+import+BuiltIn,+RobotNotRunningError

class+SudsLibraryExtension(object):
++++"""
++++Extension+on+the+SudsLibrary

++++"""
++++ROBOT_LIBRARY_SCOPE+=+'GLOBAL'++++
++++ROBOT_LIBRARY_VERSION+=+1.0

++++def+__init__(self,+LibraryName='SudsLibrary'):
++++++++"""SudsLibraryExtension+can+be+imported+with+an+optional+argument.
++++++++-+``LibraryName``:
++++++++++Default+value+for+`LibraryName`+is+SudsLibrary+if+not+given.
++++++++++The+name+can+by+any+Library+Name+that+implements+or+extends+the
++++++++++SudsLibraryExtension.
++++++++"""++++++++
++++++++try:
++++++++++++self.SudsLibrary+=+BuiltIn().get_library_instance(LibraryName)

++++++++#+This+is+useful+for+when+you+run+Robot+in+Validation+mode+or+load
++++++++#+the+library+in+an+IDE+that+automatically+retrieves+the+documen-
++++++++#+tation+from+the+library.+
++++++++except+RobotNotRunningError:
++++++++++++pass

++++def+set_binding(self,+binding,+url):
++++++++"""Set+Binding+can+be+used+to+add+a+binding+to+the+message.

++++++++Example++++Set+Binding+++++SOAP-ENV++++http://www.w3.org/2003/05/soap-envelope
++++++++"""
++++++++suds.bindings.binding.envns+=+(binding,+url)|2348307|entityMap|0|LINK|mutability|MUTABLE|url|http://www.holidaywebservice.com/HolidayService_v2/HolidayService2.asmx^0|0|3|S|0|0|0|8|C|1|6|M|1|6|A|1|0|0|0|0|1|6|6|1|6|A|1|0|0|0|0|0|I|1|6|15|1|6|17|1|0|0|0|0|0|C|0|0|0|N|0|0^^$0|@$1|2|3|4|5|6|7|20|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|21|8|@]|9|@$D|22|E|23|1|24]]|A|$]]|$1|F|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|26|8|@$D|27|E|28|J|K]]|9|@]|A|$]]|$1|L|3|M|5|N|7|29|8|@$D|2A|E|2B|J|K]]|9|@]|A|$]]|$1|O|3|P|5|N|7|2C|8|@$D|2D|E|2E|J|K]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2H|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]|$1|V|3|W|5|I|7|2J|8|@]|9|@]|A|$]]|$1|X|3|Y|5|N|7|2K|8|@$D|2L|E|2M|J|K]]|9|@]|A|$]]|$1|Z|3|10|5|N|7|2N|8|@$D|2O|E|2P|J|K]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]|$1|13|3|T|5|6|7|2S|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|2T|8|@]|9|@]|A|$]]|$1|15|3|16|5|I|7|2U|8|@$D|2V|E|2W|J|K]]|9|@]|A|$]]|$1|17|3|18|5|N|7|2X|8|@$D|2Y|E|2Z|J|K]]|9|@]|A|$]]|$1|19|3|1A|5|N|7|30|8|@$D|31|E|32|J|K]]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|33|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|34|8|@]|9|@]|A|$]]|$1|1D|3|T|5|6|7|35|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|36|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|37|8|@$D|38|E|39|J|1I]]|9|@]|A|$]]|$1|1J|3|1K|5|1L|7|3A|8|@]|9|@]|A|$1M|1N]]|$1|1O|3|1P|5|6|7|3B|8|@$D|3C|E|3D|J|1I]]|9|@]|A|$]]|$1|1Q|3|1R|5|1L|7|3E|8|@]|9|@]|A|$1M|1N]]|$1|1S|3|-4|5|6|7|3F|8|@]|9|@]|A|$]]]|1T|$1U|$5|1V|1W|1X|A|$1Y|1Z]]]]

In short Suds does not support SOAP 1.2 bindings. Development has ceased quite some time ago. For this reason the SudsLibrary does not support it either. 

Some of the differences I observed using an <a href="http://www.holidaywebservice.com/HolidayService_v2/HolidayService2.asmx" rel="nofollow noreferrer">example service SOAP 1.1/1.2</a> are: 

<ol>
<li>HTTP header <code>Content-Type</code>: 

<ul>
<li>1.2 = <code>"application/soap+xml"</code> </li>
<li>1.1 = <code>"text/xml"</code>.</li>
</ul></li>
<li>HTTP header 

<ul>
<li>1.2 = <code>Action</code> </li>
<li>1.1 = <code>SOAPAction</code></li>
</ul></li>
<li><code>Envelope Namespace</code> 

<ul>
<li>1.2 = <code>"http://www.w3.org/2003/05/soap-envelope"</code> </li>
<li>1.1 = <code>"http://schemas.xmlsoap.org/soap/envelope/"</code></li>
</ul></li>
</ol>

For each of these a seperate solution was implemented in the example below. The content type could be overwritten. The Action can be added but the SOAPAction can not be removed. The namespace can also be overwritten using the extension library. This should work for you if your service ignores the SOAPaction header attribute.

Test Case.robot

<pre><code>*** Settings ***
Library SudsLibrary
Library SudsLibraryExtension
Library Collections 

*** Test Cases ***
TC
 ${BASE_URL} Set Variable http://www.holidaywebservice.com
 ${SERVICE} Create Dictionary 
 ... name=HolidayService_v2 
 ... wsdl=HolidayService2.asmx?WSDL
 ${PORT} Set variable HolidayService2Soap12
 ${METHOD} Set variable GetCountriesAvailable

 Set Binding SOAP-ENV http://www.w3.org/2003/05/soap-envelope
 Create Soap Client ${BASE_URL}/${SERVICE.name}/${SERVICE.wsdl}
 Set Port ${PORT}

 Set Headers Content-Type application/soap+xml
 Set Headers Soapaction ${EMPTY}
 Set Headers Action "${BASE_URL}/${SERVICE.name}/${METHOD}"

 ${result} Call Soap Method ${METHOD}
</code></pre>

SudsLibraryExtension.py

<pre><code>import suds.bindings
from robot.libraries.BuiltIn import BuiltIn, RobotNotRunningError

class SudsLibraryExtension(object):
 """
 Extension on the SudsLibrary

 """
 ROBOT_LIBRARY_SCOPE = 'GLOBAL' 
 ROBOT_LIBRARY_VERSION = 1.0

 def __init__(self, LibraryName='SudsLibrary'):
 """SudsLibraryExtension can be imported with an optional argument.
 - ``LibraryName``:
 Default value for `LibraryName` is SudsLibrary if not given.
 The name can by any Library Name that implements or extends the
 SudsLibraryExtension.
 """ 
 try:
 self.SudsLibrary = BuiltIn().get_library_instance(LibraryName)

 # This is useful for when you run Robot in Validation mode or load
 # the library in an IDE that automatically retrieves the documen-
 # tation from the library. 
 except RobotNotRunningError:
 pass

 def set_binding(self, binding, url):
 """Set Binding can be used to add a binding to the message.

 Example Set Binding SOAP-ENV http://www.w3.org/2003/05/soap-envelope
 """
 suds.bindings.binding.envns = (binding, url)
</code></pre>

I am trying to test soap 1.2 services using RobotFramework. So far, we have only tested soap 1.1 services using suds library for RobotFramework, and suds is not compatible with soap 1.2.

Backwards compatibility is an option for the new services, but it would be better to have a more long-term solution. I am not an experienced programmer, though I can edit code if told what to edit and where.

What happens in the test we have for soap 1.2 services using suds is: suds is unable to interpret the response it gets from the webservice and gives this error: SAXParseException: :159:229: mismatched tag

The soap message is fine, there is no problem using it in SoapUI.

I have found some snippets online that suggest I could get suds library to work with soap 1.2 for my RobotFramework tests. But I have little programming experience and no idea how to incorporate those snippets in suds.
Someone commented on this snippet that this fixed his issue with RobotFramework and suds.

Is there someone out there willing to explain how I could make this work? I can't seem to figure it out on my own. Any suggestions would be greatly appreciated.

<pre><code>from suds.client import Client
from suds.bindings import binding
import logging


USERNAME = 'username'
PASSWORD = 'password'

# Just for debugging purposes.
logging.basicConfig(level=logging.INFO)
logging.getLogger('suds.client').setLevel(logging.DEBUG)

# Telnic's SOAP server expects a SOAP 1.2 envelope, not a SOAP 1.1 envelope
# and will complain if this hack isn't done.
binding.envns = ('SOAP-ENV', 'http://www.w3.org/2003/05/soap-envelope')
client = Client('client.wsdl',
 username=USERNAME,
 password=PASSWORD,
 headers={'Content-Type': 'application/soap+xml'})

# This will now work just fine.
client.service.someRandomMethod()
</code></pre>

snippet from: <a href="https://gist.github.com/kgaughan/858851" rel="nofollow noreferrer">https://gist.github.com/kgaughan/858851</a>

Testing Soap 1.2 service in RobotFramework using suds library

我正在尝试使用RobotFramework测试SOAP1.2服务。到目前为止，我们只使用RobotFramework的suds库测试了SOAP1.1服务，并且suds与SOAP1.2不兼容。向后兼容是新服务的一个选项，但最好是有一个更长期的解决方案。我不是一个有经验的程序员，虽然我可以编辑代码，如果被告知要编辑什么和在...

问使用suds库在RobotFramework中测试SOAP1.2服务
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用suds库在RobotFramework中测试SOAP1.2服务EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用suds库在RobotFramework中测试SOAP1.2服务
EN