-
Notifications
You must be signed in to change notification settings - Fork 615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Savon should understand and support elementFormDefault="qualified" #91
Comments
added to the wishlist for future versions under "improve the WSDL parser". |
+1. We're connecting to a .NET service that doesn't work unless the local elements include the namespace. Thanks! |
Would love to see this implemented too. Also connecting to a .NET service! |
added support for elementFormDefault="qualified" closed by 5c8ec13. the attribute is read from wsdl documents and can also be set
|
Great work! Have just tested this and confirmed it as working. Thanks very much :) |
Finally got the chance to test. Great work. |
fixes savonrb#91. the attribute is read from wsdl documents and can also be set manually via: client.request :authenticate do soap.element_form_default = :qualified end
summited by khoenshel (September 27, 2010):
I am connecting to a service where the WSDL sets elementFormDefault="qualified". From what I understand, this value can be set to 'qualified' or 'unqualified'. An over-simplified description: when set to 'qualified', all of the elements in the SOAP request need to be fully qualified, as in eimermusic's example above. This behavior is specified here: http://www.w3.org/TR/xmlschema-0/#QualLocals. An explicit setting for this style of output in the SOAP body would be nice, but if the WSDL file specifies that the elements should all be fully namespace qualified, then the elements in the SOAP body should be fully qualified. For now, I have to place the namespace in the hash keys...
The text was updated successfully, but these errors were encountered: