GeeCON Prague 2014*
The moose likes Web Services and the fly likes REST API Design Rulebook - WADL Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Web Services
Bookmark "REST API Design Rulebook - WADL" Watch "REST API Design Rulebook - WADL" New topic
Author

REST API Design Rulebook - WADL

Kim Baddeley
Greenhorn

Joined: Nov 06, 2003
Posts: 6
Hi Mark,

What is your opinion on WADL. Should a RESTful service provide one or is the standard dead in the water?

Thanks,
Kim
Mark Masse
author and iconoclast
Greenhorn

Joined: Nov 08, 2011
Posts: 20
Kim Baddeley wrote:Hi Mark,

What is your opinion on WADL. Should a RESTful service provide one or is the standard dead in the water?

Thanks,
Kim


Hi Kim,

I am a fan of the concept of making all sorts of metadata available to clients and servers that wish to "introspect" a web API's resource models and/or its data structures/schemas. While this certainly isn't a need that all clients will have but many do benefit from the kind of information that machine interfaces/contracts like WADL can provide. I have no strong bias for or against WADL, but in my crystal ball, I don't see it suddenly catching on and becoming a big part of our forward looking, client-server (REST API-oriented) web app architectures.

So, while I can relate to the ideas that inspired WADL, I am not a big fan of how it is "implemented" and I am also not sold that it adds enough value for my apps to bother with it.

If others have found it compelling and have been able to leverage it to write less boilerplate code (or whatever), I would love to hear some of those success stories.

-Mark

WRML and the REST API Design Rulebook
 
GeeCON Prague 2014
 
subject: REST API Design Rulebook - WADL