2009/4/2 Paul Sandoz <Paul.Sandoz_at_sun.com>:
>
> On Apr 2, 2009, at 1:39 PM, James Strachan wrote:
>
>> 2009/4/2 Dusan Hornik <dusan.hornik_at_atlassian.com>:
>>>
>>> Paul Sandoz wrote:
>>>
>>> Hi,
>>>
>>> Perhaps there are other ways we can improve this as well.
>>>
>>> e.g. @Produces on a template processor?
>>>
>>> Template Processor can be used to generate multiple formats html, json,
>>> etc
>>> so it's probably not a good idea.
>>
>> You could always list the full list of all the possible mime types you
>> can produce - with whatever weighting you wish (e.g. to weight HTML
>> above XML etc).
>>
>> Or maybe use a wildcard to avoid listing all the thing you can produce
>> but just weight what you prefer to generate?
>>
>> @Produces("text/html;qs=5, */*")
>>
>
> s/_at_Produces/_at_ImplicitProduces
I was just referring to your previous comment....
>>> Perhaps there are other ways we can improve this as well.
>>>
>>> e.g. @Produces on a template processor?
That we might wanna use the @Produces - with the qs=X modifier - (when
the spec has changed and Jersey supports such a thing) on template
processors. I was thinking generically, but I guess using
@ImplicitProduces is fine on a template processor such as Velocity as
thats gonna be used for implicit views too - but I kinda thought the
mime type quality (qs=X) should eventually be independent of whether
or not implicit views are used.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/