rpc/encoded operations

[apenney]

This is more of a plea than an issue, but will these eventually be supported in v3?

[2] pry(#Puppet::Util::NetworkDevice::F5::Device)> transport['System.Session'].operation('System.Session', 'System.SessionPort', :set_active_folder)
Savon::UnsupportedStyleError: "set_active_folder" is an "rpc/encoded" style operation.

I am an idiot when it comes to SOAP, so I don't know if this is a minor request or a huge impossibility.

[tjarratt]

Hey @apenney, thanks for raising this issue. I wasn't aware that Savon3 did not yet have support for rpc/encoded operations.

Poking around in the stable release, version 2, I see some integration tests that claim to test WSDLs with those operations. Have you tried using the stable release, or is there a reason why you'd like this to be in Savon 3 specifically? The reason I ask is that Savon 3 is still considered unstable, and there are a lot of features (like rpc/encoded operations, for example) that haven't been implemented yet.

[tjarratt]

Oh, just saw your comments in the issue re: renaming Savon 3. Thanks for the valuable information. Will leave this open for now with the Savon 3 label.

[apenney]

The long winded backstory is that I'm converting a puppet module over to using savon in https://github.com/apenney/puppetlabs-f5/tree/savon-implementation but I ran into a problem where my XML was making the f5 SOAP handler crash. I was looking at XML examples from their python library and I realized they extract more information from the WSDL (type information, as far as I can tell) and feed that into the XML. I decided to see if Savon 3 sent "better" XML in that regard.

I had also hoped to find a way to not have to do:

x.call(:message)[:message_response[:return][:item] and I had hoped the return from savon3 would have an easier way to get to just the "meat" of the message. So that's why I was hoping to see it in Savon 3, because we'll probably move fairly aggressively once it's considered stable. :)

[tjarratt]

Okay, that helps shine some light on what you're trying to accomplish. My suggestion would be to use Savon 2 for the time being, as I imagine Savon 3 (or whatever it becomes) will be unstable and likely to change its API for some time.

[tjarratt]

With that said, I think this is a perfectly reasonable feature request.

[tjarratt]

Hey @apenney I migrated this over to savonrb/sekken#2.