OSGi JAX-RS Connector 3.1 released

OSGi JAX-RS Connector 3.1 released

connectorEarlier this year in June we released the 3.0 version of the OSGi JAX-RS Connector together with JAX-RS 2.0. Since then a lot has happened in the project and we decided to do a 3.1 release. Below are the important features and changes that made it into 3.0 and 3.1. If you’re not familiar with the connector, these articles will get you started: Introduction, Consuming services.

  • Before 3.0 there were two bundles. The connector and the consumer. The project originally only had the connector, so the bundle was named *.connector. But we decided to rename it to be more precise. In the new structure the project is named connector and it contains two major bundles, the publisher (formally connector) and the consumer.
  • We upgraded to Jersey 2.3.1.
  • Bryan Hunt did a pull request that adds a custom @Provider in order to use Eclipse MOXy for de/serialization. I had also written a custom provider a while back, that uses Gson for this purpose. So we added two bundles that contain these custom providers.
  • The p2 repository was restructured to contain the features of the custom providers.
  • A Metatype was added to allow the configuration of the base URL. That’s useful when using tools like the Apache Felix Webconsole.
  • API was added to the consumer to be able to pass in custom client configurations. This replaces the old @Provider array and additionally allows the configuration of user credentials and other items.
  • Support for bndtools was added.
  • A tycho based build was added.
  • The project is now being built using travis-ci

We also changed the README so it no longer contains the changelog of the project. Instead we went with github releases. You can consume the connector in the usual ways: download, p2 and maven. Checkout the README for more details.

GitHub repository: https://github.com/hstaudacher/osgi-jax-rs-connector

p2 repository: http://hstaudacher.github.com/osgi-jax-rs-connector

As always, feel free to comment icon wink OSGi JAX RS Connector 2.0 released .

  • Douglas Beattie
    Posted at 1:20 am, October 22, 2013

    Apparently the your link to the GitHub repository points to a P2 repository instead.
    I poked around on GitHub and found the project at

  • Dirk Zander
    Posted at 12:49 pm, December 6, 2013

    Hello Holger,

    I am using the connector inside Gyrex-Server. On server startup endless exceptions are thrown and the server does not come up. In the stack trace I saw a call at ResourceTracker.addingService(). I guessed that could be the cause of the endless looping. So I decided to limit the service filter of the ResourceTracker to only consider certain services usnig objectClass=com.mycompany.*. And now it works!

    So for me the question arises, whether it is possible to make this service filter configurable from outside, e.g. via service property.