Thanks Sastry, I commented on the issue already.
Marek
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.
> http://java.net/jira/browse/JAX_RS_SPEC-149
>
> thanks,
> Sastry
>
> ------------------------------------------------------------------------------------------------------------------------
> *From:* Marek Potociar <marek.potociar_at_oracle.com>
> *To:* Sastry Malladi <m_sastry_at_yahoo.com>
> *Cc:* "jsr339-experts_at_jax-rs-spec.java.net" <jsr339-experts_at_jax-rs-spec.java.net>
> *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
>
>