Hello Jose,
is there any major demand/strong usecase behind this? I don't think we
would like to encourage developers to write code which does not comply
with JAX-RS spec and needs some custom proprietary "collision
resolver".. maybe if you can describe some problem which is solvable
with this ResourceComparator and does not have standard solution, we
might consider adding it. Actually if it manifests to be major issue, it
might be considered as part of some future JAX-RS spec update (but I
kind of doubt that in this case)..
Regards,
Pavel
On 6/6/12 12:26 PM, Jose Antonio Illescas Del Olmo wrote:
> It's very useful allows to developers write custom resource/methods
> selectors to overwrite default selection algorithm
>
> see: ResourceComparator [CXF]
>
>
> What do you think?
>
>