Re: JSR311: selectVariant not very useful

From: Bill Burke <>
Date: Fri, 31 Jul 2009 17:08:32 -0400

Marc Hadley wrote:
> On Jul 30, 2009, at 1:07 PM, Bill Burke wrote:
>> * I can't, in practice, ever see the use case where a resource method
>> would support a language for one media type, and not another, at least
>> where a JAX-RS service is concerned.
> I can see the case where a resource method might support one language
> for some URI template value and another language for another. Same goes
> for media type. The API supports more dynamic conneg than static
> annotations could.

Ok, I read the thread and understand why you might want the API, for the
case where you have a cache/file system/db that holds pre-compressed
data in different formats and languages and charsets. Still I can't
help thinking I'd model the web services very different in such a
scenario, like putting this information within the URL.

BTW, I only asked this question because a few reviewers of my book asked
me why you'd ever need such an API. I couldn't answer them...

Bill Burke
JBoss, a division of Red Hat