Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

  • Migration to a modern Updated 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.
  • Updated 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)Support lowlevel storage metadata. Fedora now includes a hints provider API, allowing implementations to pass such metadata as mimetype or collection membership to be passed to the low-level storage module. This would allow, for example, the low-level storage module to make decisions about where objects or datastreams are stored based on the provided metadata.
  • Legacy authentication module EOL. The legacy authentication module, deprecated since Fedora 3.4, will be phased out in the next Fedora release.
  • Expanded Spring-based configuration support. Support for Spring configuration of Fedora has been expanded to include the Server module, SOAP and REST APIs.

...

Many thanks to everyone who contributed to this release. In particular, thanks go to:

  • Jiri Kremser,

...

  • Red Hat, for his work on the Google Summer of Code project.
  • Jerry Pan, Oak Ridge National Laboratory, for contributing the hints provider support.
  • Ben Armintor, Columbia University, for his heroic efforts on further Spring-ifying Fedora.
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

...