Hi Bill,
>> I think, if someone needs different resource methods for different
>> matrix parameter values (e.g @Path("abc;gg=5") ), he've made a
>> mistake in his URI modeling. IMO the API should not support this.
> I disagree. Unlike Query parameters, Matrix parameters are part of
> the identity of the resource.
Of course they are part of the URI.
But the matrix parameter values could have any value (or e.g. every
integer value). So I don't see a use case, where you need one resource
method for one value and another resource method for another matrix
parameter value.
Let us now.
best regards
Stephan