v3.0.0

[rubiii]

This ticket continues the Wasabi v4.0 milestone ticket which was driving the development for Savon version 3 up until now.

Here is my TODO list for version 3:

• Solve performance problems #7.
• Support WSDL imports #1.
• Properly separate operations by service and port.
• Support XML Schema imports.
• Remove the dependency on HTTPI as an HTTP client.
• Parse operation input parameters and generate a map of types for the message body.
• Integrate Wasabi 4.0 with Savon so people can easily test it as soon as possible.
• Add support for message headers defined in the WSDL.
• Finish initial documentation.
• Push to GitHub!
• Add support for attributes.
• Change the response Hash format to match the request Hash format.
• Convert Hash values to SOAP values (DateTime, etc) according to the type definition.
• Support WS-Policy/WS-Addressable (see Add "addressable" namespace + Action header support #409).
• Store the proper order of parameters so we can get rid of the :order! hack.
• Support for multipart responses using the new Savon::Multipart gem.
• Maybe support relative WSDL/Schema import locations? Can't find the specification for this.
• Switch from symbols to strings (for #485)
• Implement Response.header (for #544)

Please follow this issue for updates on version 3.

[mhenrixon]

Hi, so looked at the v3 API and love where Savon is going. Unfortunately it's unusable to me due to the problem with rpc/encoded messages. Any chance that might fit into V3 some time soon? Not sure what is required but with some guidance I might be able to chip in on getting it ready should you need it.

[rubiii]

@mhenrixon the problem with rpc/encoded is, that it uses a whole different type system defined by the wsdl specification. my plan is to get the xml schema types right before thinking about that. i also don't think the type-related code is ready to be extended yet.

so ... i'm not quite sure what it takes to support this, but i'd like to postpone code for this until after the 3.0 release.

[mhenrixon]

Sounds sane I just got some more documents and since I don't even know what version I am supposed to integrate with yet I won't push for this. Might not even need it if their API changed for the better between version 6 and whatever 8+ is the current.

[noiseunion]

any ETA as to when we can hope to see an official v3.0.0?

[tjarratt]

Hey @noiseunion -- thanks for the interest. I've been trying to fix some regressions and bugs in Savon 2. It's hard to set an ETA now because there hasn't been a lot of forward progress in v3 lately.

Is there a particular reason why you'd like to use an official v3 release? My feeling is that v2 will continue to be the stable release for quite a few months after v3.0.0 is officially released.

@rubiii and I were having a discussion offline a while ago about whether v3 should be released as Savon, or under a different name. The design of v3 is so different, and the support for ruby versions has changed such that I would be hesitant to call it Savon for fear of surprising users with a huge breaking API change. Since we're discussing this issue here, would you mind sharing your thoughts?

[noiseunion]

Hey @tjarratt, thanks for the reply!

I am currently using v3 in its current state on a production site and it has been working great! I personally really like the changes you guys have made in how v3 is used in comparison to previous versions. It made it really easy for me to explore the SOAP APIs I have had to work with that are quite honestly pretty poorly documented. I am finding that to many of the developers are EXPECTING me to be using .NET to consume their services. Very frustrating. :(

I am currently at a goofy spot however. I need to implement x509 authentication for one of the API's and am having a pretty tough time figuring out how to do it using v3, or if it is even possible to do at this time. That is where my curiousity came in. Hoping for some more complete documentation on what v3 can do, and hopefully getting some better explanation on how I can use v3 with Akami to implement the required x509 authentication. I guess as a tangent here, for what I am looking to do is v2.x going to be a better choice for this particular task right now?

As to whether you keep v3 under the Savon name or not, that is totally up to you guys. I don't think the changes are a great improvement...but that is just my opinion. If you want to release and run v3 and v2 in parallel, maybe just release v3 as savonrb and keep 2.x as savon? That would allow anyone currently running 2.x to continue doing so, and those who are ready to jump to the v3 changes can do so by using the other gem.

That said, you guys have done great work! I haven't done a ton of work with SOAP, but you guys have done a great job with this gem.

[rubiii]

@tjarratt i think we should move v3 to a new repository and reset master back to v2, because that’s the current “stable” version. also, i may be able to contribute to that version from time to time and it would be nice to have a separate issue tracker for v3.

if you don’t have any objections, could you move v3 to its own branch and bring v2 back to master as a first step? still thinking about a working title for the new repository, but i will move the v3 branch as soon as something pops up.

[cyrus-one]

hi @tjarratt, for what it's worth, we've built an automation framework using savon 3, to test all our new soap & rest apis and we're really happy with it. would love to see it officially released. maybe call it 'jabón' (spanish for soap) or savon-brillant (french for shiny soap), savon-trois (soap 3)....

update: here's our test-automation project that we built for our soap api's using savon 3 (thanks again!): https://github.com/sandwichclub/bubblebath

[tjarratt]

I've just opened an issue to discuss resetting savon master back to v2 and creating a new repo. I'm not particularly fond of the idea for a few reasons I've tried to explain, but I think it's best to have this discussion in the open and make an informed decision based on community feedback.

@rubiii -- I just created a branch from the tip of master for Savon v3.

[tjarratt]

@solidlight I really appreciate the name suggestions :)

Of the three you suggested I think "jabón" is best because it sounds like Savon, but does not have the word "Savon" in it. If Savon v3 is released under a new name, it would be nice for its name to not conflict or be confusing with the existing Savon release.

[ivobenedito]

You can call it "Sabão" ... it's portuguese for soap ;)!

[noiseunion]

Sekken - Japanese for soap. ( I was feeling left out ) 😄

[tjarratt]

+1 for Sekken.

No matter what name we choose, it seems that there are few complaints about resetting master to v2 and making v3 a new repo.

@rubiii do you want to set that up? I have some time this weekend and wouldn't mind making the repo and setting up Travis CI.

Sent From A Very Small Keyboard

On Apr 4, 2014, at 12:14, JD Hendrickson notifications@github.com wrote:

Sekken - Japanese for soap. ( I was feeling left out )

—
Reply to this email directly or view it on GitHub.

[tjarratt]

Closing this issue as it has been migrated to savonrb/sekken#1