y!
Steffen
Von: Edwin Shin [ed...@fedora-commons.org]
Gesendet: Dienstag, 7. Juni 2011 16:38
Bis: fedora-commons-developers@lists.sourceforge.net
Betreff: Re: [fcrepo-dev] REST API
Steffen,
See, for example:
https://github.com/mediashelf/fedora-client/blob/master/src/main/java/com/your
@fedora-commons.org]
> Sent: Thursday, June 02, 2011 11:22 AM
> To: fedora-commons-developers@lists.sourceforge.net
> Subject: Re: [fcrepo-dev] REST API
>
> As I recall purgeDatastream used to only return a 204 status code, no
> payload. See https://jira.duraspace.org/browse/FCR
02, 2011 11:22 AM
To: fedora-commons-developers@lists.sourceforge.net
Subject: Re: [fcrepo-dev] REST API
As I recall purgeDatastream used to only return a 204 status code, no payload.
See https://jira.duraspace.org/browse/FCREPO-708
Returning a JSON array of dates was intentional, so I suppose I
mmons-developers@lists.sourceforge.net
Subject: Re: [fcrepo-dev] REST API
Hi Steffen
This does indeed seem to be the case, there is not a single REST method that
equates to API-M getDatastreams. Although as you say it is possible by
iterating each individual datastream.
I have created a JIRA issue for
>> To: fedora-commons-developers@lists.sourceforge.net
>> Subject: [fcrepo-dev] REST API
>>
>>
>> Hi,
>>
>> Currently we're switching from the API-A and API-M methods to
>> the REST API and realized that the getDatastreams method has
>> n
x27;t looked at the deleteDatastream return type, maybe someone else can
shed some light on that.
Steve
> -Original Message-
> From: Wagner, Steffen [mailto:steffen.wag...@fiz-karlsruhe.de]
> Sent: 01 June 2011 14:16
> To: fedora-commons-developers@lists.sourceforge.net
>
Hi,
Currently we're switching from the API-A and API-M methods to the REST API and
realized that the getDatastreams method has no implemented counterpart at REST.
Retrieving that data in a loop over each single datastream would be a
workaround with performance impact - that's why we try to avoi
+2 Seconded!
I've also written a REST API library (in Perl) and had the same
reaction. I certainly didn't attempt to parse the Java error
response.
Which leaves only a message such as 'Check the log file.' being
sent to the application. Not nice.
I just created a Fedora Issue for this:
Improve REST API responses
https://jira.duraspace.org/browse/FCREPO-764
-- Scott
Asger Askov Blekinge wrote:
> +1 Seconded. The Rest api functions are well thought out, but the stuff
> sent to the user is generated by appending strings, and error handling
+1 Seconded. The Rest api functions are well thought out, but the stuff
sent to the user is generated by appending strings, and error handling
is not to easy, if you do not use Java.
On Wed, 2010-08-11 at 02:55 +0200, Scott Prater wrote:
> Below are some comments from one of my developer collea
Below are some comments from one of my developer colleagues, who knows
almost nothing about Fedora, but is working on an application to ingest
objects.
Perhaps the REST API error handling and responses could be improved in
future releases? I could open a ticket for it, if others think it would
11 matches
Mail list logo
