hateoas

For a SaaS startup I'm involved in, I am building both a RESTful web API and a couple of client apps on different platforms that consume it. I think I've got the API figured out, but now I'm turning to the clients. As I've been reading about REST, I see that a key part of REST is discovery , but there seems to be a lot of debate between two different interpretations of what discovery really means: Developer discovery : The developer hard-codes copious amounts of API details into the client, such as resource URI's, query parameters, supported HTTP methods, and other details that they've

I have a HATEOAS (HAL) REST service and managed to talk to it with the code below (using halarious as a conversion engine) but when I try to merge the converters ( stallone and stallone2 ), the app will always pick up the first converter, instead of the one that is appropriate for the response type which of course leads to an error. How could I avoid duplicate retrofits that are only different in a small type detail? public interface Stallone { @GET("/discovery") Call<DiscoveryResponse> discover(); @POST() Call<LoginResponse> login(@Url String url, @Body LoginRequest secret); } public static

Let's say I have two repositories: @RepositoryRestResource(collectionResourceRel = "person", path = "person") public interface PersonRepository extends PagingAndSortingRepository<Person, Long> { List<Person> findByLastName(@Param("name") String name); } and @RepositoryRestResource(collectionResourceRel = "person1", path = "person1") public interface PersonRepository1 extends PagingAndSortingRepository<Person1, Long> { List<Person1> findByLastName(@Param("name") String name); } with one regular controller: @Controller public class HelloController { @RequestMapping("/hello") @ResponseBody public

as everyone may have noticed, there are lot of fake/rudimentary REST-APIs in the wild (which implement a HTTP-API and call it REST without following the hypertext-as-the-engine-of-application-state requirement, which led to the famous rant of Roy T. Fielding , the man who first specified the REST-paradigm). I've been unable to find any practical examples of a truly hypertext driven REST-implementation along with the associated application-specific media-type definitions for the state transitions. Are there any publicly accessible examples of such implementations? Its not an implementation in