-
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
XML arguments in operation/action tag under savon 2.0 #361
Comments
I have exactly the same problem, looking forward for an answer. |
can someone provide a wsdl for testing please? |
I'll email you the WSDL I was given. Its for a closed hotel PMS system. I'm Thanks. On Thu, Jan 10, 2013 at 5:25 AM, Daniel Harrington <notifications@github.com
|
thanks for the wsdl. so the good news is that savon 2.x correctly parses the operation names. client.call(:post_transaction) you can get a list of all operations names via: client.operations but unfortunately, there is no way of adding attributes to the tag right now. |
Yes, everything works great except for adding those attributes. I had a relatively easy time of migrating the syntax given your excellent documentation. There is another action that I use that doesn't require attributes in the action tag and I was able to get it to work. For the moment I have downgraded back to savon 1.2 until we can add attributes to the action tag. Thanks! |
pushed the local attributes = { 'PosID' => 'ABC321', 'RoomID' => '128', 'Surname' => 'HERNANDEZ' }
client.call(:post_transaction, attributes: attributes) |
Works great now. Thanks! Can I expect this as an official gem anytime soon? If not I'll go ahead with just using master. |
it will be in the next release. i don't have a release date for this yet, but i'll keep you posted. |
Sounds good. Thanks. |
@rubiii 👍 |
Hi. I am currently in the process of upgrading to savon 2.x from 1.2 and have hit a bit of a wall. I have an obscure API that I must use that requires arguments other than the operation name to be in the SOAP action tag.
For example:
In savon 1.x I had something like:
Where the second and third arguments to the request method yielded an action tag of:
So far under savon 2.0 I have not been able to figure out a way to force Gyoku to use an !attributes hash when generating the action/operation tag. I've even looked through the latest Savon code to no avail.
I would prefer to not have to generate the entire message and use the :xml option (overriding Savon Builder). Is there something I am overlooking to accomplish this or can it be added as an option in a new release? Thanks!
The text was updated successfully, but these errors were encountered: