hi Scott,

to be quite honest, I don't know, but it is going to be soon.

In the meantime, if you are bootstraping the Application yourself, the
best way to get a Configurable instance would be registering a Feature
in your Application. The Feature will receive a FeatureContext when the
application is initialized and you should be able to programmatically
add extensions there. This should be a portable way of doing it, since
you would only rely on JAX-RS API.

Hope this helps.

Carlos.


El 20/3/18 a las 20:08, Scott Lewis escribió:
> Hi Carlos,
>
> Thanks for the pointers.  This is great.
>
> What is the timeframe for release of Aries impl of jax-rs-whiteboard?
>
> Thanks,
>
> Scott
>
> On 3/20/2018 11:33 AM, Carlos Sierra Andrés wrote:
>> You could also entertain
>> https://github.com/apache/aries-jax-rs-whiteboard
>>
>> it is an implementation of a whiteboard for JAX-RS applications. It is
>> specified how to register applications and extensions just like the ones
>> you need. It is based upon CXF but you only need to use JAX-RS and OSGi
>> API.
>>
>> The only thing is that there are only snapshots published at the moment.
>> If it is not a deal breaker for you I believe you could give it a go.
>>
>> Bests.
>>
>> Carlos.
>>
>> El 20/3/18 a las 18:52, James Carman escribió:
>>> You can use JaxrsServerBeanFactory in OSGi just fine. With that, you
>>> can
>>> add all the providers you want. You can check out Microbule for
>>> inspiration:
>>>
>>> https://github.com/Microbule/microbule
>>> On Tue, Mar 20, 2018 at 1:34 PM Scott Lewis <[email protected]>
>>> wrote:
>>>
>>>> I'm programmatically using cxf in an osgi environment.  I'm using the
>>>> servlet class: org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet,
>>>> and want to create and an impl of javax.ws.rs.core.Configurable to
>>>> register extensions (e.g. json support, etc).
>>>>
>>>> Is there a cxf jaxrs impl of javax.ws.rs.core.Configurable in that
>>>> I can
>>>> create programmatically, and use to register extensions like
>>>> ContextResolver, etc?
>>>>
>>>> Thanksinadvance,
>>>>
>>>> Scott
>>>>
>>>>
>>>>
>

Reply via email to