added a comment - - edited
The API I've implemented in my patch adds one operation:
This produces (in XML) a document like so:
The idea would be that clients can retrieve the bounds and then apply them in the usual fashion by POSTing back to the featuretype resource. One technical oddity is that in order to provide this custom XML format I had to make a bit of the XStreamPersister public (so I can encode the CRS more succinctly). Is this ok?
I'm open to other designs, I could see it making sense to just POST (maybe with a new declared projection) to the calculate resource instead of having to make two requests.
Either way, this patch needs some polish: the routes currently only work for /workspaces/ws/featuretypes/ft but should also allow /workspaces/ws/datastores/ds/featuretypes/ft . There's also a Freemarker template missing before the HTML serialization will work.