Implement PUT /objects/pid in Legacy REST API

[BHSPitMonkey]

As discussed in IRC; Title says it all.

Let the magic begin.

[ajs6f]

When issuing a PUT to /objects/{pid}, what is the payload supposed to be exactly? Object profile XML?
1:23
jcoyne left the room (quit: Read error: Connection reset by peer).

1:24
BHSPiMonkey
(In other words, the same format as the GET response for the same url?)

1:24
ajs6f
And if we're in the same container and in the same classpath, a simple singleton might be enough.

1:24
cbeer
BHSPiMonkey: what's PUT?

1:24
ajs6f
But JNDI should be fine.

1:24
BHSPiMonkey
cbeer: I'm referring to the legacy API, sorry

1:25
cbeer
BHSPiMonkey: ok, i don't think we've implemented a PUT /objects/{pid}

1:25
ajs6f
I don't think we have a PUT-to-/objects/{pid}
What cbeer said.

1:25
BHSPiMonkey
oh, okay

1:25
ajs6f
Would you like one?

1:25
cbeer
BHSPiMonkey: in fcrepo 3, it's just an update-object-properties method
and we don't have any of those yet, really.

1:25
ajs6f
I think we could very easily do a PUT object proile to that endpoint.
We have a JAXB-annotated class that could be used.
Want to file a ticket?
1:26
BHSPiMonkey
ajs6f: if it's that easy, that would be cool; otherwise, no worries

1:26
ajs6f
1:26
Just file a ticket and watch the magic happen!

[ajs6f]

Done. There is now a PUT update method at that endpoint which accepts object profile either in XML or JSON. It will accept an incomplete object profile and mutate only the data that exist in the message. See:
0c48e63