[aerogear-dev] REST-based API Versioning

Erik Jan de Wit edewit at redhat.com
Thu Aug 28 04:39:33 EDT 2014

> On our Face2Face meeting we briefly talked about this and I think the "accept header" solution was the one that had most fans. I think QMX added that it is better for migration. One thing we were not clear on (I think): What are HATEOS defined semantics?
+1 for accept header
> Besides the what (headers vs. URI), I think we should think about possible implementations, to switch different versions.
> Not sure, but wouldn't it be possible to inject an annotated SenderService into the RESTful endpoint, based on header values ? 
> We could have a default impl (version 1.0.0) and an alternate one, that is injected if the accept header indicate API version 1.1

Don’t know of anything that can do something like that automatically and rest easy doesn’t provide anything for versioning. I would propose to keep it simple and let UPS internally use the latest version and provide something like a servlet filter that converts old calls to the new API or dispatches to another rest end point


More information about the aerogear-dev mailing list