On Sep 17, 2012, at 10:46 AM, Sergey Beryozkin wrote:
> On 17/09/12 15:27, Santiago Pericas-Geertsen wrote:
>>
>> On Sep 17, 2012, at 6:53 AM, Sergey Beryozkin wrote:
>>
>>>
>>>>>>>
>>>>>>>>> 7. ContainerResponseContext.getHeaders& getStringHeaders - both return mutable maps, the latter method only supports remove operations: can we have getHeaders() only ? A single method dedicated to modifying response headers ?
>>>>>>>>
>>>>>>>> The getStringHeaders() provide a convenient string-based view of getHeaders(). There are many cases where this is useful. We may updated the javadoc so that getStringHeaders() do not indicate support for removal operations, if you want, but the method should stay.
>>>>>>>>
>>>>>>> If you can agree to make this view read only then it would simply things IMHO
>>>>>>
>>>>>> Ok, I don't have any problems with removing the mutability requirement from the javadoc.
>>>>>
>>>>> That simplifies things a bit
>>>>
>>>> Done.
>>>
>>> Can you please do the same for ClientRequestContext ?
>>>
>>> Have few more questions.
>>>
>>> 1. Is it ValidationException when we have different filter classes having the same NameBinding value ?
>>
>> ValidationException is only for collecting BV constraint validations.
>>
>
> What do we do then in this case ? Is it a valid one ?
It's valid. See Section 6.5.2.
-- Santiago