-
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
Setting headers and namespaces #9
Comments
looks like something you could easily abstract in your application.
or whatever fits your style. |
Interesting idea, but not all the methods are gets; a singleton soap client is essential (easily fixed above); and the parameters are not fixed -- hence my original suggested api outline that retained the block. Are you against providing methods to add headers and namespace changes at the SOAP client layer? |
need to ask if you're using savon without the wsdl, cause i have a little problem with globally setting the namespace. the default for all global/per request options is that the per request options are always favored before the global ones. now savon can be used with and without its wsdl object, which also sets the namespace uri. to be consistent with all other options, when using the wsdl, the namespace uri retrieved from the wsdl would need to be used instead of the global one. you know what i mean? don't know if that meets your requirements though. |
I'm using WSDL. It makes sense for the per request options to have priority, but are they not additive? When I tried without the namespaces option, the namespace was not correctly picked up from the WSDL, that's why I am using that option. |
it's ok. will add these features in the next version and leave the issue open until it's released. |
I would like to see general purpose http header support as well so those of us who have to deal with http basic auth vs wsse can use savon |
http authentication is on my todo-list, but please stick to the topic when commenting on an issue. if you really feel you need to push the topic, just open another issue. |
added to the official todo list at: http://rubiii.tadalist.com/lists/1459816/public |
added support for global soap header and namespaces to the dev branch. this was long overdue. will be included in the next release. please take a look at: |
released version 0.7.2 including a fix for this issue. |
Fixes issue with WSDL message element having no part element.
Hi,
I'm wrapping a SOAP service and so have to repeat the same
soap block assignments at every SOAP call. Ideally, I'd like to "push" these
assignments up a level.
For example, currently I have something like:
Where I'd like to get to is:
with something like:
Any idea how I might get close to this? Or is there a better way? Thanks.
The text was updated successfully, but these errors were encountered: