On Sep 25, 2007, at 7:05 AM, Paul Sandoz wrote:
>
> I don't think it makes sense to support:
>
> /collection.xml/1
> /collection.xml/1.xml
>
> The suffices only makes sense on last path segment of the URI.
>
The use of sub-resource methods will make this quite complex and
possibly counter-intuitive. Would it make sense to match the URIs
above but to simply ignore the extensions on the path segments
matched to the parent class. E.g.
@UriTemplate(value="collection" extensions=true)
public class SomeResource {
@HttpMethod
SomeCollection getAll(@UriExtensions String exts[]) {
...
}
@UriTemplate(value="{id}" extensions=true)
@HttpMethod
SomeItem getItem(@UriParam("id") String itemId, @UriExtensions
String exts[]) {
...
}
}
With the above you want both
GET /collection.xml, and
GET /collection/1.xml
to work so it could be tricky to disallow GET /collection.xml/1.xml
since the URI to resource class matching algorithm first has to match
the SomeResource class before it can match the getItem method.
Marc.
---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.