Why the slow WADL uptake? [closed]

by

I think the main reason why WADL doesn’t gain popularity is that it might bring back to life all those problem we had with SOAP and WSDL. To me, the interoperability aspect is the single most important aspect of web-services.
By following the RESTful way of using pure HTTP standards you get interoperability “for free”. Once you need a document to describe the services, there will be different client frameworks (or different servers frameworks) that will interpret this document differently.
Once different frameworks auto-generate code from WADL you will have to deal with the interoperability problems again.

The lack of standards is the weakness and strength of the RESTful way, let’s give the simple approach a chance. (even though we really enjoy automatic code generation 🙂 )

More Related Contents:

  1. HTTP GET with request body
  2. Best practices for API versioning? [closed]
  3. If REST applications are supposed to be stateless, how do you manage sessions?
  4. Representational state transfer (REST) and Simple Object Access Protocol (SOAP)
  5. HTTP POST with URL query parameters — good idea or not?
  6. REST API Best practice: How to accept list of parameter values as input [closed]
  7. When do I use path params vs. query params in a RESTful API?
  8. Transactions in REST?
  9. How to QUEUE a new build using VSTS REST API
  10. What is RESTful programming?
  11. secure api data from calls out of the app
  12. S3 REST API and POST method
  13. REST Content-Type: Should it be based on extension or Accept header?
  14. How to send a message successfully using the new Gmail REST API?
  15. Are there any naming convention guidelines for REST APIs? [closed]
  16. How to expose a RESTful Web Service using Meteor
  17. Rest Standard: Path parameters or Request parameters
  18. REST vs JSON-RPC? [closed]
  19. What’s the currently recommended way of performing partial updates with Web API?
  20. Azure Websites Kudu REST API – Authentication
  21. REST api: requesting multiple resources in a single get [duplicate]
  22. How to format Swagger 2.0 text descriptions?
  23. How to create new build pipeline using Azure DevOps REST API?
  24. Delete multiple records using REST
  25. What is the difference between a HTTP-Get and HTTP-POST and why is HTTP-POST weaker in terms of security
  26. How do I get the body of a web request that returned 400 Bad Request from Invoke-RestMethod
  27. ‘Best’ practice for restful POST response
  28. When in my REST API should I use an envelope? If I use it in one place, should I always use it?
  29. Swagger UI passing authentication token to API call in header
  30. REST API DESIGN – Getting a resource through REST with different parameters but same url pattern

Leave a Comment