[aerogear-dev] REST-based API Versioning

Sebastien Blanc scm.blanc at gmail.com
Thu Aug 28 04:42:01 EDT 2014

On Thu, Aug 28, 2014 at 10:39 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> >
> > 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
+1 I like the Servlet Filter approach

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140828/4d6c5272/attachment.html 

More information about the aerogear-dev mailing list