[jax-rs-spec users] [jsr339-experts] Re: Re: OSGI support

From: Sastry Malladi <>
Date: Tue, 20 Dec 2011 13:38:50 -0800 (PST)

I added some comments to the issue.  The gist is that, we may not need to add anything to the spec itself regarding OSGI, but please take a look at my comments and provide your thoughts.  thanks.


 From: Marek Potociar <>
To: Sastry Malladi <>
Cc: "" <>
Sent: Friday, December 16, 2011 2:33 AM
Subject: Re: [jsr339-experts] Re: [jax-rs-spec users] Re: OSGI support
Thanks Sastry, I commented on the issue already.


On 12/16/2011 02:05 AM, Sastry Malladi wrote:
> I'd love to see that addressed though, in 2.0  - Here is the JIRA I filed.
> thanks,
> Sastry
> ------------------------------------------------------------------------------------------------------------------------
> *From:* Marek Potociar <>
> *To:* Sastry Malladi <>
> *Cc:* "" <>
> *Sent:* Saturday, December 10, 2011 12:11 PM
> *Subject:* [jax-rs-spec users] [jsr339-experts] Re: OSGI support
> Hi Sastry,
> JAX-RS 2.0 will most likely not address OSGi deployments. Feel free to file a new JIRA issue for that though.
> Marek
> On 12/10/2011 02:09 AM, Sastry Malladi wrote:
>> I've a question on how we intend to support JAX-RS based resources deployed in an OSGI container.
>> For example, the JAX-RS container itself (e.g jersey or other implementations) will be packaged as an OSGI bundle.
>> Individual resource applications will also be packaged and deployed as OSGI bundles. However, these application bundles
>> may have some provider classes that are to be loaded by the JAX-RS container, but it has no access to them. Typically we
>> set-up the dependency from application to JAX-RS bundle, but not the other way around.
>> We have addressed this kind of a problem internally through some offline registration mechanism, but wanted to know what
>> is the official JAX-RS spec way to do this ?
>> thanks,
>> Sastry