[jax-rs-spec users] [jsr339-experts] Re: Re: FYI: ResourceContext API proposed

From: Marek Potociar <>
Date: Tue, 28 Aug 2012 15:43:35 +0200

On Aug 28, 2012, at 2:42 PM, Bill Burke <> wrote:

> Comment on issue too?

I think it will be more convenient to discuss via email.

> From a CDI perspective, I'm against this idea as there is already sufficient APIs in CDI:
> #1 CDI's BeanManager interface provides this functionality already
> #2 The Sub-resource locator itself could be an injected CDI bean.
> #3 Components needed by the sub-resource locator could be injected into the parent and passed in via a constructor or setter methods

For some reason I thought you're not a big fan of introducing a hard dependency between JAX-RS and CDI. Are you suggesting we're only supporting this with CDI-based JAX-RS resources? Or would it make sense to specify how BeanManager should be used in the implementation of the API in runtimes where CDI is available/enabled?

> BUT...
> Resteasy does have something similar to access JAX-RS @Context injected things programmatically.

Right, as you may have noticed, the proposed API is based on a Jersey-specific API that our users seem to use quite heavily. Also, I think we really need to keep in mind that life's not revolving just around CDI.


> On 8/24/2012 12:34 PM, Marek Potociar wrote:
>> Experts,
>> as a resolution of a critical issue
>> a new ResourceContext API has
>> been introduced. Please see the change here:
>> Your review feedback & comments are welcome.
>> Many thanks,
>> Marek
> --
> Bill Burke
> JBoss, a division of Red Hat