wsdl --> grpc

[ghost]

this is really nice.

I was wondering if you think its going to be difficult to do the opposite.
Use case:
You get given a WSDL to some Microsoft SOAP system that you have to talk to and its like " ah shit here we go again" :). How am i going to easily talk to it using golang.

SO maybe there is a way to point the generator at the WSDL and generate bindings for it.

[tgulacsi]

There are a lot of WSDL client generators, such as https://github.com/hooklift/gowsdl
But wsdl is quite complex, with lot of branches (document or literal), possibly integrated xsd spec - you'll have to send xml to that SOAP endpoint, so a generated .proto file won't be enough.

I don't have a use case for this now, sorry.

[mmundy3832]

I just found this comment while looking for exactly the same tool suggested by ghost.

I am currently attempting to port .Net Framework application with a WSDL-defined interface (from ONVIF.org) into a .Net Core app in Visual Studio 2019. Since WCF is not supported in .Net Core It looks like I will need to convert a WSDL file to a proto file by hand to use gRPC.

So there is at least a use case now.

[tgulacsi]

Sorry, but SOAP is quite complex, just opposite of it's name.
And WSDL multiplies it.
And the wsdl->proto transformation is lossy, you won't generate the same wsdl from that proto file (maybe except when you cheat and just reuse the original wsdl).

But please prove me wrong - I have to communicate with predefined wsdl, and sometimes the wsdl is enforced...

[mwelser]

really would be great to have something like this - also having the problem right now that I have to talk with a go client with a legacy soap service and the WSDL to go generators are not really working 100%

having a kind of grpc proxy that my golang client only needs to communicate via grpc would be great

[tgulacsi]

Yes, that would be great.

For calling SOAP, I'm using wsdl-analyzer.com to generate stub request, then use valyala/fasttemplate to generate such xml.
For responses, I use miku/zek to generate a struct for the answer, tweak it, and use the standard encoding/xml to parse.