wow... great, thanks!
Carlos.
El 19/12/17 a las 18:24, Sergey Beryozkin escribió:
> Hi Carlos
>
> Should be fixed now...
>
> Sergey
> On 07/12/17 18:14, Carlos Sierra Andrés wrote:
>> Hi again Sergey,
>>
>> so I just checked with Glassfish Jersey 2.26 and it injects the
>> Application into the F
Hi Carlos
Should be fixed now...
Sergey
On 07/12/17 18:14, Carlos Sierra Andrés wrote:
Hi again Sergey,
so I just checked with Glassfish Jersey 2.26 and it injects the
Application into the Feature with:
@Provider
public static class MyFeature implements Feature {
@Override
Thank you for your quick reply!
Just one more question. If I got right what you said, in my typical example:
rour suggestion would be to do something like this:
It is not clear to me how I should behave with the OAuthContextProvider,
SearchContextProvider or MultipartProvider. I suspect I ca
Hi Carlos
On 19/12/17 11:01, Carlos Sierra Andrés wrote:
h... this is a very legit question.
I had already answered as if François was meaning JAX-RS Features.
If you don't mean JAX-RS features, but CXF or Karaf features, then I
think there is no way to register them, yet.
So far we are fo
Thanks Carlos,
I will take a look.
François
Le 19/12/2017 à 14:58, Carlos Sierra Andrés a écrit :
> Hi François,
>
> yes... it should.
>
> Here you can find a test in which we register a Feature. The spec also
> mandates in the latest draft that the properties used to register the
> applicatio
h... this is a very legit question.
I had already answered as if François was meaning JAX-RS Features.
If you don't mean JAX-RS features, but CXF or Karaf features, then I
think there is no way to register them, yet.
So far we are focusing on implementing the spec but I guess we won't
discar
I mean CXF-features like org.apache.cxf.jaxrs.swagger.Swagger2Feature
Le 19/12/2017 à 14:54, Jean-Baptiste Onofré a écrit :
> What do you mean by "features" ? Karaf or CXF features ?
>
> Regards
> JB
>
> On 12/19/2017 11:51 AM, Francois Papon wrote:
>> Hi Carlos,
>>
>> I'm interesting by this and
Hi François,
yes... it should.
Here you can find a test in which we register a Feature. The spec also
mandates in the latest draft that the properties used to register the
application be present in the configurables.
https://github.com/apache/aries-jax-rs-whiteboard/blob/master/jax-rs.itests/sr
What do you mean by "features" ? Karaf or CXF features ?
Regards
JB
On 12/19/2017 11:51 AM, Francois Papon wrote:
Hi Carlos,
I'm interesting by this and I would like to know if this is the same
approach for features ? (Swagger feature for example)
Thanks,
François
Le 19/12/2017 à 14:36, Ca
Hi Carlos,
I'm interesting by this and I would like to know if this is the same
approach for features ? (Swagger feature for example)
Thanks,
François
Le 19/12/2017 à 14:36, Carlos Sierra Andrés a écrit :
> Hello Matteo,
>
> you can just publish the filters as OSGi services advertising the
> i
Hello Matteo,
you can just publish the filters as OSGi services advertising the
interfaces you want them to be registered by. I am not aware of any
specific example for CXF services, but in the tests you can see how
"extensions" can be registered:
https://github.com/apache/aries-jax-rs-whiteboard/
Hello,
In OSGi I usually configure my CXF REST endpoints using blueprints as
follows:
I would like to avoid blueprint-based configuration and switch to
declarative services. I saw an example on how to do this with OSGi
whiteboard:
https://github.com/apache/aries-jax-rs-whiteboard/tree/m
12 matches
Mail list logo