Hi Josh I've updated the JAX-RS layer in DOSGi such that it will now discover JAXRS (and CXF specific providers) which have been registered as (global) OSGI services. At the moment I've decided not to use a ServiceTracker and instead a calling BundleContext is asked to exercise a filter expression which should catch JAXRS MessageBodyReader, MessageBodyWriter, ExceptionMapper, as well as CXF RequestHandler, ResponseHandler & ParameterHandler. I'll attempt to optimize it later on....
One can disable such queries for such providers and also insist that only those global providers which have identified themselves (through a specific property) that they will work reliably with CXF can be used. Alternatively, one can register an array of service/endpoint -specific providers by using "org.apache.cxf.rs.provider" property, when registering an application service. Will document it tomorrow Give it a try please whenever you get a chance and let me know if it works for you cheers, Sergey Josh Holtzman wrote: > > Hi Sergey. Yes, we are using JAXB with both JAX-RS and JAX-WS endpoints. > > Josh > > On Aug 21, 2009 6:28 PM, "Sergey Beryozkin" <sbery...@progress.com> wrote: > > Hi Josh > > Can you please let me know if JAXB is being used for your JAX-RS endpoints > ? > I've spotted that for HTTP Service based JAX-RS endpoints no AegisProvider > is being set - I'would actually like JAXB being used by default for JAXRS > endpoints which will be consistent with the expectations of JAX-RS users > in > general - but I'd like to confirm first that JAXB is working ok in your > case... > > thanks, Sergey > >> Sergey, > Thanks again for the detailed documentation you've provided in > this thread. > I was ab... > > -- View this message in context: http://www.nabble.com/RE%3A-Integrating-JAX-RS-runtime-into-DOSGi-tp24127832p25138636.html Sent from the cxf-dev mailing list archive at Nabble.com.
