tag:blogger.com,1999:blog-2708349453904691513.post5073953703794168217..comments2022-03-27T17:28:15.522+02:00Comments on Martin Krasser's Blog: New features in grails-jaxrs 0.3Martin Krasserhttp://www.blogger.com/profile/11765963540395771125noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-2708349453904691513.post-6345007384364610562010-06-09T15:39:02.999+02:002010-06-09T15:39:02.999+02:00@Jianfeng Take a look at the unit and integration ...@Jianfeng Take a look at the unit and integration tests: http://grails-jaxrs.googlecode.com/svn/trunk/jaxrs/test/<br /><br />Hope that helps. If not, post a message with more details to the grails-jaxrs-discussion group at http://groups.google.com/group/grails-jaxrs-discussMartin Krasserhttps://www.blogger.com/profile/11765963540395771125noreply@blogger.comtag:blogger.com,1999:blog-2708349453904691513.post-48002021221570945812010-06-09T14:47:15.669+02:002010-06-09T14:47:15.669+02:00Hi Martin,
Many thanks for the post and the plugi...Hi Martin,<br /><br />Many thanks for the post and the plugin. I get stuck with doing unit test with the REST API. Could you please give me some advice?<br /><br />Many thanksJThttps://www.blogger.com/profile/01691282196833839280noreply@blogger.comtag:blogger.com,1999:blog-2708349453904691513.post-40984589989629209922010-02-02T07:50:19.488+01:002010-02-02T07:50:19.488+01:00Jonathan, glad to see your interest in grails-jaxr...Jonathan, glad to see your interest in grails-jaxrs. Although I haven't used REST API versioning in my projects so far I have a preference for URI-based versioning because of simplicity, especially when you introduce schema changes that are not backwards-compatible. Using URI-based versioning ensures that existing clients can continue to work on older versions while a content-negotiation-based approach requires clients to always include some kind of vendor MIME media type in the Accept header with additional version information. If the header is omitted the server will likely serve the latest version which might break the client. Furthermore, using a content-negotiation-based approach prevents you to e.g. send links to older versions by email. This is not an issue when using URI-based versioning. Please handle my statements with care :) I don't have much experience with REST API versioning. <br /><br />So far I didn't have plans to add versioning support to the plugin but you're welcome to add a feature request to the project's issue tracker (or start a discussion in the grails-jaxrs-discuss Google group). <br /><br />Cheers,<br />MartinMartin Krasserhttps://www.blogger.com/profile/11765963540395771125noreply@blogger.comtag:blogger.com,1999:blog-2708349453904691513.post-12220880518146418132010-02-02T03:03:05.617+01:002010-02-02T03:03:05.617+01:00This is great, we're in the early stage of inv...This is great, we're in the early stage of investigating this plugin for use with a new system we're developing in grails. One thing I didn't see in the doc, do you have a suggestion for how to best handle versioning? I've seen proponents of both URI based versioning and content negotiation methods and would like to know:<br /><br />1. Do you have a suggestions for one or the other?<br />2. Are there plans of building this into the framework?Jon Toddhttps://www.blogger.com/profile/04805503928238028826noreply@blogger.com