Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Panel
Children Display
styleh3

On this page:

Table of Contents

Fedora 3.6 Release Notes

Release Date: August 7, 2012:

We are proud to announce the release of Fedora 3.6. Some of the notable new features include:

  • Migration to a modern Web Services framework. Fedora 3.6 incorporates work from the Google Summer of Code project to move from the aging Axis 1.3 library to Apache CXF. This allows Fedora to support MTOM, which provides a 33% size efficiency over Base64 encoded transmission.
  • REST API Validation failure response codes changed to 400. If a REST API management operation results in a validation failure (e.g. ingest FOXML validation, validation failure via the DOObjectValidator module) the HTTP response code is now 400. Previously Fedora reported a generic Server Failure 500 response code. The response body indicates the nature of the validation error.
  • (populate metadata to akubra/hints api)
  • Legacy authentication module EOL The legacy authentication module, deprecated since Fedora 3.4, will be phased out in the next Fedora release.

You are encouraged to download this new release and give it a spin. Please let us have your comments and feedback via the mailing lists, and of course please let us know of any problems you discover.

For a detailed list of features and bugfixes comprising this release see the tables below.

Acknowledgments

Many thanks to everyone who contributed to this release. In particular, thanks go to Jiri Kremser, a doctoral student at Masaryk University in the Czech Republic, for his work on the Google Summer of Code project.

Note
titleTomcat Compatibility

Tomcat 5.5 and earlier are no longer supported. This release has been extensively tested with Tomcat 6.0.x, and is also known to work with Tomcat 7.0.x

Note
titleREST API

As part of ongoing cleanup efforts, REST API responses have been fixed so that they are now fully compliant with their declared schema. This means that some responses might be slightly different when compared to those from earlier releases. For more information, see the overarching issue in Jira

Features and Improvements

...

Bug Fixes

...

Previous Release Notes

...