Rate this page:
28 July 2010With pleasure, Atlassian presents the Atlassian REST Plugin 2.1.
Atlassian REST 2.1, when paired with Seraph 2.2, provides more reliable use of REST resources by scripts and programs. The full explanation is a bit technical. Here's a developer's way of putting it into human-readable words:
You know how after a while you get logged out of JIRA or Confluence. As a person you notice that pretty easily because the page just looks different. But a program isn't that smart. It doesn't know that it has suddenly been logged out and is now doing things as 'anonymous' and not 'jsmith'. The new REST + Seraph combination means they get an error message instead of just suddenly becoming 'anonymous' when using REST.
Do you generate your REST API documentation using the Jersey WADL? With version 2.1 of the REST plugin, you can now have JSON examples as well as XML in your generated documentation. The plugin provides a new doclet based on that allows JSON examples. You will need to change your to use this doclet.
This release also enables self-expansion of entities, along with other improvements described below.
|REST-141||atlassian-rest-common doesn't export all packages||Jul 15, 2010||Sep 28, 2015||Luis Miranda [OOO until 2018]||Luis Miranda [OOO until 2018]||RESOLVED||Fixed|
|REST-140||Enable self expanding functionality||Jul 08, 2010||Sep 28, 2015||Luis Miranda [OOO until 2018]||Luis Miranda [OOO until 2018]||RESOLVED||Fixed|
|REST-138||Framework doesn't handle inherited ListWrapper fields||Jul 02, 2010||Sep 28, 2015||Luis Miranda [OOO until 2018]||Luis Miranda [OOO until 2018]||RESOLVED||Fixed|
|REST-136||add request attribute for /rest/ to force os_authType for seraph||Jun 30, 2010||Sep 28, 2015||Justus Pendleton||Justus Pendleton||RESOLVED||Fixed|
|REST-134||Allow for JSON examples in generated REST documentation||Jun 28, 2010||Sep 28, 2015||Luis Miranda [OOO until 2018]||Luis Miranda [OOO until 2018]||RESOLVED||Fixed|
Rate this page: