> 2) The sub-resource locator, that returns a resource for further path
> matching, should not be annotated with an @GET method.
Hmmm, so the subresource can't support different methods for GET,
POST, etc.? Does it have to be a class with essentially one method
(or one per path selector)?