Developers, please take note:
When Fedora 3.3 is released in a few weeks, there will be a small
change to the REST API that *may* require you to make a minor
modification to your code in order to work with 3.3. This will be
documented in the release notes, but we wanted to provide advance
notice.
You're affected if your application uses REST API URLs ending in .xml,
including the following:
objects/nextPID.xml
objects/{pid}.xml
objects/{pid}/datastreams.xml
objects/{pid}/datastreams/{dsID}.xml
objects/{pid}/versions.xml
objects/{pid}/methods.xml
In these cases, you must change the URLs to the following form:
objects/nextPID?format=xml
objects/{pid}.xml?format=xml
objects/{pid}/datastreams?format=xml
objects/{pid}/datastreams/{dsID}?format=xml
objects/{pid}/versions?format=xml
objects/{pid}/methods?format=xml
As you can see, the change removes the currently-supported ".xml"
shortcut from the REST API endpoints. This fixes an API design
problem that prevents certain information from being accessed via the
REST api. Specifically, it makes the object and datastream profiles,
when the PID or Datastream ID happens to end in ".xml", inaccessible.
For more detail on this, see
https://fedora-commons.org/jira/browse/FCREPO-522
The good news is that you can update your applications right away if
you want -- the ?format=xml form works for 3.2.x and will continue to
work for 3.3.
Thanks,
Chris
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Fedora-commons-developers mailing list
Fedora-commons-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
