Hi Jose,
another (standard, non Jersey specific) way to do this directly in the
resource method is described
in the other e-mail i have just posted to the list.
~Jakub
On 18.8.2011 13:08, Jose Antonio Illescas Del Olmo wrote:
> Pavel (one more time sorry),
>
>
> I see one manner to access to contentType negotiation: On custom
> ContainerResponseFilter you can access to content-type-negotiation
> across ContainerRequest.getAcceptableLanguage(List<MediaType>)
>
>
> I posted here for someone interested on this.
>
> Regards
>
>
>
> On 16/08/2011 17:30, Pavel Bucek wrote:
>> well, you have your "ugly" solution. Currently I don't see the way
>> how you could obtain result of content negotiation process (I think
>> this was here some time back and result was basically the same).
>>
>> Btw, how many content types (approx) are you supporting per resource?
>>
>> On 8/16/11 5:12 PM, Jose Antonio Illescas Del Olmo wrote:
>>> Please any suggestion?
>>>
>>> I needed the "default contentType" after jersey
>>> content-type-negotiation? (I need on my REST method, annotated with
>>> @POST, @PUT)
>>>
>>>
>>> On 11/08/2011 16:04, Jose Antonio Illescas Del Olmo wrote:
>>>> Can get the "default" contentType selected by Jersey on my method?
>>>>
>>>> Please note that Jersey (and any JAX-RS implementation)
>>>> calculates the content type to invoke the method with valid media
>>>> type...
>>>
>>>
>>
>>
>
>