What I would do is trying to keep compatibility for a release or two (that can be years :D) and then remove the old Content-Type completely.
JAX-RS allows for the @Produces annotation to specify several possible content-types, and it even has a mechanism for negotiating such types (or so I read here: [1]<http://java.net/projects/jersey/lists/users/archive/2009-10/message/475> ). Rubén Pérez TELTEK Video Research www.teltek.es [1]<http://java.net/projects/jersey/lists/users/archive/2009-10/message/475> http://java.net/projects/jersey/lists/users/archive/2009-10/message/475 2012/10/17 Greg Logan <[email protected]> > Hi folks, > > We appear to have a small cluster of issues (MH-8767, MH-9184, MH-9219, > MH-9228) which all relate to the calendaring, the CA, and Unicode. The > question I present to you here is what happens when fixing a bug changes > the REST API? The fix for MH-9219 is simple and, in my opinion, low > risk, but it does change the REST API for the calendar subsystem. Can > we apply this to 1.4, or does it need to wait for 1.5? > > I think it should go in, but I know there have been some very strong > feelings with regard to changing APIs. In this case, the API change > merely changes the mimetype from plain text to calendaring data. > > Thoughts? > > G > > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ >
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
