-
Notifications
You must be signed in to change notification settings - Fork 98
FAQ
- Check that you have started the
com.eclipsesource.jaxrs.publisher
bundle.
- Check that the responsible provider bundle e.g.
com.eclipsesource.jaxrs.provider.moxy
is active.
You have two options:
- Install the Eclipse Maven Tooling and run the launch config JAX-RS Connector Build.launch.
- Step into
build/com.eclipsesource.jaxrs.build/
folder and executemvn clean verify
By default the publisher registers the services using the context path /services
. This means an OSGi service that is annotated with @Path( "/foo" )
will be available using the path /services/foo
. This context path is configurable using the OSGi configuration admin. You can configure the service using the service.pid com.eclipsesource.jaxrs.connector
and the property root
to define a custom path.
The JAX-RS consumer throws a RequestException
when the server returns a 4xx or 5xx status. The RequestException
has methods to get information about the failed request.
With Jersey 2.7 the Jersey team decided to compile the library using Java 7, see the changelog. For this reason the connector bundles also need to use Java 7.
The connector uses an AllServiceTracker which tracks all services and publishes them as resources if possible. If you would like to limit the services tracked you can implement your own ResourceFilter
and register it as a service. Please note that it must be available in the container before the publisher starts.