On 9/17/2012 12:40 PM, Sergey Beryozkin wrote:
> On 17/09/12 17:30, Bill Burke wrote:
>> Santiago. I thought you were spot on in the comments. Either the user
>> can use explicit @OPTIONS resource methods and/or write a response
>> filter. We just need to make sure response filters are run in error
>> conditions.
>>
>
> That introduces a possible inconsistency between the default runtime
> processing and the custom one - in the latter all depends on the user
> doing that interceptor - which is problematic on its own: the runtime
> knows better what HTTP methods are supported by a given handler as
> opposed to the user code.
>
I'll have to review what you're proposing, but I don't see whether it
matters if there is inconsistencies or not as long as the HTTP
specification is honored. I know people are doing a lot of different
things with OPTIONS.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com