4 ms·

Thanks! I figured the same. OpenAPI seems to be it. WSDL on the other hand seems to be dead and/or unusable. Even one of its creators described it as a "train

Thanks! I figured the same. OpenAPI seems to be it. WSDL on the other hand seems to be dead and/or unusable. Even one of its creators described it as a "train wreck" :)

machinshin_ 11y ago
Oh gods yah. WSDL should die painfully in a fire with all the people in its standards committee
- junto 11y ago
  The basic WSDL stuff is OK. It's the WS-n extensions that are truly the Zed of this world.
mrweasel 11y ago
>WSDL on the other hand seems to be dead Yeah, it's not. It's still what people in big enterprises do, or what people who want to do a quick API use. If you're a .NET developer it's pretty easy to consume WDSL/SOAP services, so you might be more inclined to just use it when creating your own webservices. There's of cause also the group that doesn't really know what they're doing, who just slaps a webservice method decorator on whatever internal function they wish to expose. Those are usually the worst APIs. But yes, WDSL is a train wreck.