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 > 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/blob/master/jax-rs.itests/src/main/java/test/JaxrsTest.java#L1674 > > I hope this helps. > > Carlos. > > El 19/12/17 a las 11:14, matteo escribió: >> 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/master/jax-rs.example/src/main/java/org/apache/aries/jax/rs/example >> >> What is the right approach to combine CXF filters such as >> CrossOriginResourceSharingFilter, OAuthContextProvider and all that with the >> whiteboard approach? Is there any example or documentation page that >> explains how to configure CXF JAX-RS servers and CXF providers in this way? >> >> Thank you very much, >> Matteo >> >> >> >> ----- >> matteo >> -- >> Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
