Application name-bindings do apply to providers this Application
provides (filters, interceptors).
What is the rule when some of the providers have their own name-bindings
? Do they end up with their own name-bindings + those belonging to
Application ?
I think it might be better if provider-specific name-bindings were
preferred in such cases - it would be similar to the way
resource-specific @Produces/_at_Consumes take precedence over root resource
annotations
Thanks, Sergey