[jax-rs-spec users] [jsr339-experts] Re: Not a big fan of @NameBinding, remove it?

From: Marek Potociar <>
Date: Wed, 20 Feb 2013 14:50:57 +0100

I can only repeat myself. We're past the point of removing and adding pieces of API just because you are "not a big fan" of them. This API has been discussed at length and often offers a simple and nice way for binding providers.


On Feb 20, 2013, at 12:03 AM, Bill Burke <> wrote:

> If your annotation has a qualifier, then @NameBinding really isn't a very efficient pattern to implement a filter or interceptor. For example, let's say you had a @MaxAge annotation that triggered adding a Cache-Control header with a qualified max-age:
> @MaxAge(100)
> @GET
> public String get() {...}
> The @NameBinding filter would have to inject ResourceInfo and look up the @MaxAge annotation each and ever request to set the value. It is much better to implement a DynamicFeature in this case so you can pre-initialize the filter with the annotation's value.
> --
> Bill Burke
> JBoss, a division of Red Hat