On 21/05/17 18:22, Christian Kaltepoth wrote:
I agree using @Priority is a viable option. But as I implied earlier, this approach (apart from solving the issue shown with MVC vs custom CSRF mapper) raises the question - why to support two ExceptionMapper<MyObject> or ParamConverters in general. Perhaps it does not really matter, but I guess we'd like to avoid supporting the solutions where the developers will start thinking about dropping 3 ExceptionMapper<MyObject>, and ordering them 1, 2, 3 and making each of them, say, 1 and 2, not to map, for 3 to do the final mapping :-).
That said, may be this example is hypothetical, and using @Priority just works, though I thought I'd suggest a 'default mapper' around javax.* idea too...