poke object graph through the REST API #54
Conversation
| import static org.slf4j.LoggerFactory.getLogger; | ||
|
|
||
| @Component | ||
| @Path("/rest/{path: .*}/fcr:graph") |
There was a problem hiding this comment.
@ajs6f I couldn't get this to play nice as a part of the FedoraNodes routing.. it seemed like some of the IT requests were hitting the rdf-producing endpoints instead of the object profile one..
There was a problem hiding this comment.
I have no idea what FedoraNodes is/does, so I'll start there. More soon.
There was a problem hiding this comment.
Okay, FedoraNodes seems to be the endpoint formerly known as "fcr:describe". It's not clear to me why there's any difficulty-- you're not doing anything that plenty of other working endpoints aren't doing. What exactly are the paths that are failing?
There was a problem hiding this comment.
Maybe this is a question for @barmintor then..
When I tried to put this method in FedoraNodes, several of the integration tests (perhaps all of them?) that tried to get the ObjectProfile or DatastreamProfile XML/JSON responses were getting this response instead. I assume in the absence of an Accept header, JAX-RS magically chooses a response, and ended up choosing wrong.
Maybe this isn't a problem in the long term (if we kill of those profile responses), but was more than I wanted to bite off..
|
merged separately. |
This is just a thought exercise to poke SPARQL/UPDATE queries through the REST API and have them modify object properties. Obviously a lot of things wrong with this, but hey, it actually seems to (mostly) work.
cc: @ajs6f