On 25/10/11 20:55, Santiago Pericas-Geertsen wrote:
> Hello Experts,
>
> As you know, we already support filters as well as a few different ways in which they can be bound to resource classes and methods (by name or global/static or dynamic). However, all these filters are intended to be executed _after_ requests are matched to resource methods.
>
> There are some use cases in which requests need to be transformed _before_ the matching algorithm kicks off. An example of this is a filter that overrides the HTTP method, e.g. using X-HTTP-Method-Override. In a servlet environment, this could be achieved by using a servlet filter. But, of course, JAX-RS runs on many other environments.
>
> Should we look at supporting these type of pre-matching filters/transformers/routers? (Clearly, I don't have a good name for them yet).
>
So it's method level interceptors basically which are supported now -
clearly it's not ideal to get a security filter written per every method ?
+1 to having such request handlers
> -- Santiago
>
>
--
Sergey Beryozkin
http://sberyozkin.blogspot.com
Talend - http://www.talend.com